/gaia-sprint-status
user-facingWhat it does
/gaia-sprint-status displays the current sprint
dashboard -- a read-only summary of every story in the active
sprint with its status, points, risk level, and assignee. After
rendering the dashboard, it reconciles any drift between story
files and the sprint tracking file to keep them in sync.
When to use it
- You want a quick overview of sprint progress during a standup or check-in.
- You need to see which stories are ready for development, in review, or blocked.
- You suspect the sprint tracking file has drifted from the actual story file statuses.
Prerequisites
-
A sprint must be active.
.gaia/state/sprint-status.yamlmust exist. Run/gaia-sprint-planfirst to create it.
How to invoke
/gaia-sprint-status
No arguments needed.
What it does step by step
-
Render dashboard
Reads the sprint tracking file and produces a formatted dashboard
showing each story's key, title, status, points, risk, and
assignee. If any story has
risk: HIGH, appends recommended mitigations. -
Reconcile drift
Compares each story file's frontmatter against the sprint
tracking cache. If any story's status has changed (for example,
moved from
in-progresstoreviewby/gaia-dev-story), auto-corrects the tracking file and shows the corrections. - Suggest next actions Based on the dashboard state, suggests the most relevant next command -- such as implementing a ready story, running reviews, or starting a retrospective.
Inputs
| Input | Source | Description |
|---|---|---|
| Sprint tracking | .gaia/state/sprint-status.yaml |
Contains the sprint metadata and story list. |
| Story files | .gaia/artifacts/implementation-artifacts/epic-{epic_key}-*/ |
Read for reconciliation -- frontmatter status is the source of truth. |
Outputs
This command produces text output only. If reconciliation detects
drift, it updates sprint-status.yaml to match the
story files.
Example session
> /gaia-sprint-status
Sprint-4 Dashboard (2 weeks, 21 points)
| Key | Title | Status | Points | Risk |
|---------|--------------------------|--------------|--------|--------|
| E5-S12 | Add webhook retry logic | in-progress | 3 | medium |
| E5-S14 | Improve error messages | done | 2 | low |
| E3-S9 | Dashboard search | ready-for-dev| 5 | high |
| E3-S10 | Export CSV | review | 3 | low |
| E4-S6 | Rate limiting middleware | ready-for-dev| 5 | medium |
| E4-S7 | API key rotation | ready-for-dev| 3 | high |
Progress: 2/21 points done (9%) | 1 in-progress | 1 in review
Reconcile: E5-S14 status corrected (was ready-for-dev, now done).
Suggested:
/gaia-dev-story E3-S9 -- highest-priority ready story
/gaia-review-all E3-S10 -- story awaiting review
What to run next
/gaia-dev-story-- implement the next ready story./gaia-review-all-- run reviews on stories in review status./gaia-correct-course-- adjust scope if stories are blocked./gaia-retro-- when all stories are done, run the retrospective.
Troubleshooting
"sprint-status.yaml not found"
No sprint has been planned yet. Run /gaia-sprint-plan first.
"sprint-status.yaml is malformed"
The YAML file may have been manually edited incorrectly. Check for syntax errors (indentation, unclosed quotes) and fix them before re-running.