Skip to Content
Cheat Sheet/check-milestone

/check-milestone

Assess progress toward a specific milestone — what’s done, what’s left, what’s at risk — to support release and timeline decisions.

When to use it

Run this when a milestone deadline is approaching, when a stakeholder asks “are we going to hit M2?”, or when you’re deciding whether to ship now or wait. The command reads the milestone definition from docs/PRODUCT-ROADMAP.md, pulls every issue tagged with that milestone, counts them by status, computes completion percentage, and surfaces risks: stuck In Progress tickets, blocked dependencies, missing acceptance criteria on unshipped work.

The output is a milestone health report you can share verbatim — “M1 is 73% done, 4 tickets blocked, 2 at risk for the 2026-08 target.” That’s the input to a release decision; it doesn’t make the decision itself.

Use /sprint-status for board-wide health (unscoped); use this when the question is specifically about one milestone. Use /release-decision when you’ve reviewed the milestone status and now need to make the actual go/no-go call.

How it fits

Inputs are the roadmap definition and current board state. Output is a health report that feeds either the release-decision gate (go/no-go) or another grooming pass (close out the gap).

What it does (quick)

  • Reads milestone definition from docs/PRODUCT-ROADMAP.md
  • Pulls every issue tagged with the milestone label
  • Counts by status and computes completion percentage
  • Surfaces blockers — issues with unresolved Depends on: lines
  • Calls out at-risk items — stalled In Progress, missing acceptance criteria, ambiguous Definition of Done
  • Compares actual pace against target date; flags slip risk
  • Outputs a single milestone health report; modifies no board state
  • /sprint-status — board-wide health (unscoped); use this when you want the whole picture, not one milestone
  • /groom-backlog — the natural follow-up when this command shows the milestone needs more ready tickets
  • /release-decision — downstream; uses this report as the input to a ship/wait decision

Canonical spec: .claude/commands/check-milestone.md

Last updated on
/sprint-status/work-ticket