/sprint-status
Get a fast, read-only overview of board health — column counts, bottlenecks, stale tickets, 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 board snapshot: how many tickets sit in each column, what’s been In Progress or In Review the longest, what’s likely blocked, what landed this week. It is explicitly read-only — nothing moves, nothing closes, 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 column thin? In Review pile-up?),
during a standup-style check-in to share board 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 (move tickets), /work-ticket
(pick up the top of Ready), or /review-pr
(clear the In Review pile). This command is observation only.
How it fits
Reads the board, 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 tickets per column and flags imbalances (Ready empty? In Review piling up?)
- Lists In Progress work with age, calls out stale items (no activity in X days)
- Lists pending reviews with wait time and who needs to act
- Surfaces blockers — declared
Depends on:lines that haven’t resolved - Lists what landed in Done this week (recent completions)
- Outputs a single overview report; modifies no board 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