| name | bmad-sprint-status |
| description | Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status" |
Sprint Status Workflow
Goal: Summarize sprint status, surface risks, and recommend the next workflow action.
Your Role: You are a Developer providing clear, actionable sprint visibility. No time estimates — focus on status, risks, and next steps.
Conventions
- Bare paths (e.g.
checklist.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).{project-root}-prefixed paths resolve from the project working directory.{skill-name} resolves to the skill directory's basename.
On Activation
Step 1: Resolve the Workflow Block
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml — defaults{project-root}/_bmad/custom/{skill-name}.toml — team overrides{project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Set mode = {{mode}} if provided by caller; otherwise mode = "interactive"
Jump to Step 20
Jump to Step 30
Continue to Step 1
Load {project_context} for project-wide patterns and conventions (if exists)
Try {sprint_status_file}
sprint-status.yaml not found.
Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.
Exit workflow
Continue to Step 2
Read the FULL file: {sprint_status_file}
Parse fields: generated, last_updated, project, project_key, tracking_system, story_location
Parse development_status map. Classify keys:
- Epics: keys starting with "epic-" (and not ending with "-retrospective")
- Retrospectives: keys ending with "-retrospective"
- Stories: everything else (e.g., 1-2-login-form)
Map legacy story status "drafted" → "ready-for-dev"
Count story statuses: backlog, ready-for-dev, in-progress, review, done
Map legacy epic status "contexted" → "in-progress"
Count epic statuses: backlog, in-progress, done
Count retrospective statuses: optional, done
Pick the next recommended workflow using priority:
When selecting "first" story: sort by epic number, then story number (e.g., 1-1 before 1-2 before 2-1)
1. If any story status == in-progress → recommend `dev-story` for the first in-progress story
2. Else if any story status == review → recommend `code-review` for the first review story
3. Else if any story status == ready-for-dev → recommend `dev-story`
4. Else if any story status == backlog → recommend `create-story`
5. Else if any retrospective status == optional → recommend `retrospective`
6. Else → All implementation items done; congratulate the user - you both did amazing work together!
Store selected recommendation as: next_story_id, next_workflow_id, next_agent (DEV)
## Sprint Status
Pick an option:
1) Run recommended workflow now
2) Show all stories grouped by status
3) Show raw sprint-status.yaml
4) Exit
Choice:
Run `/bmad:bmm:workflows:{{next_workflow_id}}`.
If the command targets a story, set `story_key={{next_story_id}}` when prompted.
### Stories by Status
- In Progress: {{stories_in_progress}}
- Review: {{stories_in_review}}
- Ready for Dev: {{stories_ready_for_dev}}
- Backlog: {{stories_backlog}}
- Done: {{stories_done}}
Display the full contents of {sprint_status_file}
Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.
Exit workflow
Load and parse {sprint_status_file} same as Step 2
Compute recommendation same as Step 3
next_workflow_id = {{next_workflow_id}}
next_story_id = {{next_story_id}}
count_backlog = {{count_backlog}}
count_ready = {{count_ready}}
count_in_progress = {{count_in_progress}}
count_review = {{count_review}}
count_done = {{count_done}}
epic_backlog = {{epic_backlog}}
epic_in_progress = {{epic_in_progress}}
epic_done = {{epic_done}}
risks = {{risks}}
Return to caller
Check that {sprint_status_file} exists
is_valid = false
error = "sprint-status.yaml missing"
suggestion = "Run sprint-planning to create it"
Return
