Skip to main content
command CX Codex

milestone-tracker · qdhenry — Claude Code command: what it does, how to install

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

no license ★ 1,357 updated 2026-03-01

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/milestone-tracker.md
Open on GitHub

What milestone-tracker 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.

What it helps with

  • 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 for the agent

  • 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

How to install milestone-tracker

Manually: 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 to install milestone-tracker in Claude Code?

Save the command file to .claude/commands/milestone-tracker.md within your project repository.

What does milestone-tracker do?

It scans issue trackers and repository history to evaluate milestone progress, model completion probabilities, and highlight blocked tasks.

What prerequisites are needed to run milestone-tracker?

You need local git access along with a connected Linear MCP server or GitHub milestone data accessible via the GitHub CLI.

Similar slash commands

All slash commands for Notes, tasks and projects →

milestone-tracker by other authors comes first.

milestone-tracker davila7 milestone-tracker is a Claude Code command that generates project milestone reports with progress, schedule risks, and completion forecasts for a sprint, quarter, or other period. CX Codex +1 335installs tracker-sync Gordon Mickel tracker-sync projects a flow spec into Linear, GitHub, GitLab, or Jira, then reconciles issue body, status, and comments in both directions. CX Codex +1 ★ 730repo stars Linear Automation Claude Office Skills Linear Automation automates Linear issue tracking, Git branch and PR syncing, and two-week cycle planning through project-mcp tools. CX Codex +1 4,800installs gsd-new-milestone open-gsd The gsd-new-milestone Claude Code skill starts a fresh milestone cycle in an existing project. It gathers the next goals, updates planning files, then prepares requirements and a roadmap. CX Codex +1 583installs issue-tracker clhbid The issue-tracker Claude Code skill defines terms and conventions for GitHub issues. It activates for issue and board work in clhbid repositories. CX Codex +1 795installs status-report-generator travisjneuman The status-report-generator Claude Code skill builds project status reports from Git activity, task context, and milestone tracking. It can create weekly updates, sprint reviews, and stakeholder reports. CX Codex +1 145installs agent-backlog-autopilot relatedb The agent-backlog-autopilot Claude Code skill takes one agent-backlog task from selection through a pull request. It pauses after the draft checks pass and waits for a human to mark the PR ready for review. CX Codex +1 ★ 423repo stars

From the same set112

The whole set →
dependency-mapper The dependency-mapper command connects code dependencies, Linear tasks, and Git history into project maps. Use it to spot cycles, blockers, and task order. CX Codex +1 ★ 1,357repo stars test-engineer test-engineer writes unit, integration and end-to-end tests for the code you just finished, then reports coverage by line, branch and function. Useful when a feature works but nothing guards it. CX Codex ★ 1,357repo stars audit-layer-boundaries audit-layer-boundaries analyzes architectural layer boundaries in Rust projects. It catches mixed responsibilities, misplaced database logic, and boundary leaks. CX Codex +1 ★ 1,357repo stars skill-generator-agent skill-generator-agent turns a skill spec into files on disk: SKILL.md, helper scripts, reference docs. Then it checks frontmatter and layout. CX Codex ★ 1,357repo stars audit-dependencies audit-dependencies audits dependency direction in Rust projects and flags layer violations. Use it when reviewing architecture or preparing a refactor. CX Codex +1 ★ 1,357repo stars build-skill build-skill walks a new Claude skill through four agents: requirement questions, file generation, validation, docs. You approve the spec before any file appears. CX Codex +1 ★ 1,357repo stars spec-elicitation spec-elicitation conducts a rigorous interview to turn rough feature concepts into detailed technical specifications before writing code. CX Codex +1 ★ 1,357repo stars audit-ports-adapters The audit-ports-adapters command audits ports and adapters in Rust code, checking trait placement, implementations, and whether use cases depend on abstractions. CX Codex +1 ★ 1,357repo stars

Project sponsors

Companies that keep this analytics open