# Sprint Status - Multi-Mode Service
The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml
You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
Modes: interactive (default), validate, data
⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.
Set mode = {{mode}} if provided by caller; otherwise mode = "interactive"
Jump to Step 20
Jump to Step 30
Continue to Step 1
Try {sprint_status_file}
Exit workflow
Continue to Step 2
Read the FULL file: {sprint_status_file}
Parse fields: generated, 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)
If any story has status `drafted`, treat as `ready-for-dev` (legacy status)
Count story statuses: backlog, ready-for-dev, in-progress, review, done
Count epic statuses: backlog, contexted
Detect risks:
- Stories in review but no reviewer assigned context → suggest `/bmad:bmm:workflows:code-review`
- Stories in in-progress with no ready-for-dev items behind them → keep focus on the active story
- All epics backlog/contexted but no stories ready-for-dev → prompt to run `/bmad:bmm:workflows:create-story`
- Stories in ready-for-dev may be unvalidated → suggest `/bmad:bmm:workflows:validate-create-story` before `dev-story` for quality check
Pick the next recommended workflow using priority:
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 retrospectives are optional → recommend `retrospective`
6. Else → All implementation items done; suggest `workflow-status` to plan next phase
Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate)
Pick an option:
1) Run recommended workflow now
2) Show all stories grouped by status
3) Show raw sprint-status.yaml
4) Exit
Choice:
Display the full contents of {sprint_status_file}
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_contexted = {{epic_contexted}}
warnings = {{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
Read file and verify it has a development_status section with at least one entry
is_valid = false
error = "development_status missing or empty"
suggestion = "Re-run sprint-planning or repair the file manually"
Return
is_valid = true
message = "sprint-status.yaml present and parsable"