# milestone-tracker

milestone-tracker aggregates milestone data from Linear, GitHub, and git history to calculate burn-down velocity and spot schedule risks.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/project/milestone-tracker.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/qdhenry-milestone-tracker

## What it does

This command pulls milestone definitions across Linear, GitHub, and repository tags. It inspects commit history and issue status to evaluate delivery pace, estimate remaining days, and model potential delay distributions.

The output lays out current deliverable health, identifies bottlenecks, and maps cross-task dependencies along the critical path. Without a configured Linear MCP connection or existing GitHub milestone tracking, the command cannot compute realistic progress metrics.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/milestone-tracker.md` — Call it with /milestone-tracker. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/milestone-tracker.md` — Call it with /prompts:milestone-tracker. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/milestone-tracker.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/milestone-tracker.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/project/milestone-tracker.md

## When to use it
- Calculate team burn-down velocity from recent commit history
- Spot blocked issues threatening sprint deadlines
- Map task dependencies across critical release paths
- Consolidate Linear and GitHub milestones into a single report

## Example prompts
- Run /milestone-tracker to evaluate project release dates
- Assess risks and blocker issues for our active milestones
- Generate a milestone timeline report using Linear and git history

## Similar
- [tracker-sync](https://affpapa.org/en/nevibecode/commands/tracker-sync.md) — command · ★ 730 repo stars
- [Linear Automation](https://affpapa.org/en/nevibecode/skills/linear-automation.md) — skill · 4800 installs
- [gsd-new-milestone](https://affpapa.org/en/nevibecode/skills/gsd-new-milestone.md) — skill · 583 installs
- [issue-tracker](https://affpapa.org/en/nevibecode/skills/issue-tracker.md) — skill · 795 installs
- [status-report-generator](https://affpapa.org/en/nevibecode/skills/status-report-generator.md) — skill · 145 installs
- [agent-backlog-autopilot](https://affpapa.org/en/nevibecode/skills/agent-backlog-autopilot.md) — skill · ★ 423 repo stars

## Other versions with the same name
- [milestone-tracker · davila7](https://affpapa.org/en/nevibecode/commands/milestone-tracker.md) — 335 installs

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
