/sprint-status
Get a fast, read-only overview of bead queue health — queue counts, bottlenecks, stale beads, recent completions — without modifying any state.
When to use it
Run this any time you want to know “where are we?” without committing to act. The command produces a queue snapshot: how many beads are ready, claimed, in-review, or closed this week, what has been in-progress the longest, what’s likely blocked. It is explicitly read-only — nothing is claimed, nothing is closed, nothing changes. Think of it as the gemba walk done by phone: you observe, you don’t intervene.
Use this before /groom-backlog to decide
whether grooming is needed (ready queue thin? in-review pile-up?),
during a standup-style check-in to share bead state with someone
else, or at end-of-day to capture what shipped.
Don’t use this when you need to act on what you find — that’s the
job of /groom-backlog (complete DoR so beads surface via bd ready),
/work-ticket (claim the top of the ready queue),
or /review-pr (clear the in-review pile). This command is observation only.
How it fits
Reads bead state, produces a snapshot, hands the operator a decision point. If action is needed, it routes to grooming; if not, the snapshot is the deliverable.
What it does (quick)
- Counts beads by state and flags imbalances (ready queue empty? in-review pile-up?)
- Lists claimed beads with age, calls out stale items (no activity in X days)
- Lists pending reviews with wait time and who needs to act
- Surfaces blockers — dependency edges that haven’t resolved
- Lists what closed this week (recent completions)
- Outputs a single overview report; modifies no bead state
Related commands
/groom-backlog— the natural follow-up when the snapshot says action is needed/check-milestone— the milestone-focused sibling: same observational shape, but scoped to one milestone instead of the whole board/create-ticket— when the snapshot surfaces a missing ticket
Canonical spec: .claude/commands/sprint-status.md