Skip to main content
command

milestone-tracker — Claude Code command: project milestone reports

Generate a project milestone report with progress, schedule risks, and completion forecasts. Choose a sprint, quarter, or another time period.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command project-management/milestone-tracker
Open on GitHub

What milestone-tracker does

The command reviews project activity, remote branches, and recent releases, then produces a milestone report. It covers delivery pace, dependencies, critical paths, team capacity, and blockers. You can request a sprint, quarter, or custom-period view.

Milestone details come from .github/milestones/ or a Linear integration. Git activity is counted from the last 30 days, so a project with little commit history gives the report less context. The output includes completion-date forecasts, risk assessments, and schedule recommendations.

What it helps with

  • check progress against a project milestone
  • spot blockers that threaten delivery dates
  • review sprint velocity and burn-down trends
  • compare possible milestone completion scenarios

Example prompts for the agent

  • Review milestone progress for the current sprint: /milestone-tracker --sprint.
  • Analyze project delivery for the quarter: /milestone-tracker --quarter.
  • Summarize every project milestone: /milestone-tracker --all.

How to install milestone-tracker

1claude-code-templates

npx claude-code-templates@latest --command project-management/milestone-tracker

2Manually: put the files in place

.claude/commands/milestone-tracker.md

Call it with /milestone-tracker. For all projects use ~/.claude/commands/

Questions about milestone-tracker

How do I install milestone-tracker in Claude Code?

Run npx claude-code-templates@latest --command project-management/milestone-tracker, then use the command file .claude/commands/milestone-tracker.md.

What does milestone-tracker do?

It creates a report on milestone progress, delivery pace, dependencies, and risks. The report also provides schedule forecasts and recommendations.

Where does milestone-tracker get milestone data?

It reads milestone information from .github/milestones/ or a Linear integration. Git activity and recent releases provide additional project context.

Source text

milestone-tracker.md · MIT
---
allowed-tools: Bash, Read, Grep, Glob
argument-hint: "[time-period] | --sprint | --quarter | --all"
description: Track and analyze project milestone progress with predictive analytics
---

# Milestone Tracker

Track and monitor project milestone progress with comprehensive analytics: **$ARGUMENTS**

## Current Project Context

- Project activity: !`git log --oneline --since="30 days ago" | wc -l` commits
- Active branches: !`git branch -r | wc -l` remote branches
- Recent releases: !`git tag -l --sort=-creatordate | head -5`
- Milestone data: @.github/milestones/ or Linear integration

## Task

Generate comprehensive milestone tracking report analyzing project delivery progress:

**Time Period**: Use $ARGUMENTS or default to current sprint/quarter

**Analysis Dimensions**:
1. **Milestone Progress Tracking**
   - Current milestone completion rates
   - Velocity trends and burn-down analysis
   - Critical path identification
   - Dependency mapping and risk assessment

2. **Predictive Analytics**
   - Completion date predictions with confidence intervals
   - Risk-adjusted timeline recommendations
   - Resource allocation optimization
   - Scenario planning (what-if analysis)

3. **Health Indicators**
   - Schedule adherence metrics
   - Team capacity utilization
   - Blocker identification and impact
   - Quality vs delivery balance

**Output**: Interactive milestone dashboard with visual progress indicators, predictive analytics, risk assessments, and actionable recommendations for milestone delivery optimization.

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set804

The whole set →
create-worktrees Pulls every open pull request through GitHub CLI and sets up a separate git worktree for each branch under ./tree/. Useful when you want several PRs checked out at once without switching branches in the main checkout. 351installs test-automation-orchestrator This command inspects test files and project configuration, then helps plan parallel, sequential, or conditional test runs and CI/CD pipeline execution. 350installs setup-ci-cd-pipeline Configures CI/CD pipelines for GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins with automated testing, security gates, and deployment flows. 346installs branch-cleanup A Claude slash command that finds merged and stale branches, checks them before deletion, and tidies up both local and remote refs. 342installs nextjs-scaffold Sets up a structured Next.js application with App Router, security headers, ESLint, and image optimization. 334installs setup-kubernetes-deployment Configures Kubernetes manifests and policies for an existing project. It automates container readiness checks, ingress routing, auto-scaling, and production deployment setups. 334installs create-database-migrations A Claude slash command that generates database migration files with versioning and rollback methods. Useful when you change a schema and don't want to hand-write up/down. 329installs unity-project-setup Scaffolds a standardized Unity project with structured Assets directories, URP configs, core C# managers, and Git LFS tracking via Claude Code. 303installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor