Efficient Milestone Tracker

Track and analyze project milestone progress with automated data collection from git history, issue trackers, and release tags to produce comprehensive delivery analytics.

When to Use This Command

Run this command when...

• Sprint or quarterly milestone reviews require data-driven progress reports with delivery metrics
• You need to assess whether the project is on track to meet upcoming deadlines based on current velocity
• Stakeholders need a clear view of what has been delivered, what is in progress, and what is at risk
• You want to compare actual delivery against planned milestones to identify patterns in estimation accuracy
• Release planning requires analysis of recent delivery velocity and remaining scope

Quick Start

Copy
# .claude/commands/efficient-milestone-tracker.md
---
name: Efficient Milestone Tracker
description: Track milestone progress with git analytics and delivery metrics
command: true
---
Track milestones: $ARGUMENTS

1. Collect data from git history, tags, and branches
2. Map commits and PRs to milestones and features
3. Calculate velocity, burndown, and completion rates
4. Identify at-risk items and delivery projections
5. Generate milestone tracking report

Copy
# Invoke the command
claude "/efficient-milestone-tracker Q1 2026 progress report"

# Expected output
# > Collecting milestone data for Q1 2026...
# >   Git activity: 342 commits across 28 branches
# >   Releases: v2.1.0, v2.2.0, v2.3.0 (3 releases)
# >   Contributors: 6 active developers
# > Milestone Progress:
# >   Authentication Overhaul: 100% (completed week 4)
# >   Payment Integration: 78% (12/15 tasks, on track)
# >   Admin Dashboard: 45% (9/20 tasks, at risk)
# >   API v3 Migration: 60% (6/10 tasks, on track)
# > Velocity: 14.2 tasks/week (trending up from 12.8)
# > Projection: Admin Dashboard needs 2.5 more weeks at current velocity
# > Report saved: reports/milestone-Q1-2026.md

Core Concepts

Concept	Description
Automated Collection	Gathers delivery data from git commits, tags, branches, and issue trackers automatically
Velocity Calculation	Computes task completion rate over time to project future delivery dates
Risk Assessment	Flags milestones where current velocity is insufficient to meet the deadline
Trend Analysis	Compares velocity across sprints or weeks to identify acceleration or deceleration patterns
Delivery Projection	Estimates completion dates based on remaining scope and current velocity

Milestone Tracking Dashboard
==============================

  Milestone              Progress    Status     ETA
  ---------------------  ----------  ---------  ----------
  Auth Overhaul          [========]  Complete   Week 4
  Payment Integration    [======  ]  On Track   Week 10
  Admin Dashboard        [====    ]  At Risk    Week 12.5*
  API v3 Migration       [=====   ]  On Track   Week 11

  * At Risk: current velocity (14.2/wk) insufficient
    for remaining scope (11 tasks) by deadline (Week 11)

  Velocity Trend (tasks/week):
  W1: 10.5 | W2: 11.2 | W3: 12.8 | W4: 14.2
  Trend: +1.2/week (accelerating)

Configuration

Parameter	Description	Default	Example	Required
$ARGUMENTS	Time period or milestone name to track	current sprint	"Q1 2026", "Sprint 14"	No
data_source	Source for milestone definitions	auto-detect	"github-milestones", "linear"	No
velocity_window	Number of weeks to average for velocity	4	8	No
include_contributors	Break down progress by contributor	false	true	No
output_file	Path for the tracking report	reports/milestone-{period}.md	"status.md"	No

Best Practices

1. Define milestones with measurable deliverables -- Milestones like "improve performance" cannot be tracked. Define them as "reduce p95 latency below 200ms" or "complete 15 API endpoints."

2. Track weekly for accurate velocity -- Running the tracker weekly produces enough data points for meaningful velocity trends. Monthly tracking misses important fluctuations.

3. Address at-risk milestones immediately -- When the tracker flags a milestone as at risk, take action: reduce scope, add resources, or adjust the deadline. Early intervention prevents missed deadlines.

4. Compare estimates versus actuals -- Use historical milestone data to improve future estimation accuracy. If milestones consistently take 1.3x the estimated time, calibrate estimates accordingly.

5. Share tracking reports with stakeholders -- Automated, data-driven milestone reports build trust with stakeholders by showing transparent progress based on actual delivery metrics rather than subjective assessments.

Common Issues

Insufficient git history for velocity calculation: New projects or newly onboarded repositories may not have enough commit history. Ensure at least 2-3 weeks of tracked data before relying on velocity projections.

Milestone definitions not in sync with tracker: If milestones are defined in a tool (GitHub, Linear) that the tracker cannot access, the progress mapping will be incomplete. Configure API access for your issue tracker.

Velocity skewed by non-coding tasks: Weeks with meetings, planning, or documentation produce lower commit counts, skewing velocity downward. Use a longer velocity_window (8 weeks) to smooth out these variations.