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"
<action>Jump to Step 20</action>
<action>Jump to Step 30</action>
<action>Continue to Step 1</action>
Try {sprint_status_file}
<output>❌ sprint-status.yaml not found.
Run /bmad:bmm:workflows:sprint-planning to generate it, then rerun sprint-status.
<action>Exit workflow</action>
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:
Validate all statuses against known values:
<output>
⚠️ Unknown status detected: {{#each invalid_entries}}
{{key}}: "{{status}}" (not recognized)
{{/each}}Valid statuses:
Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue without fixing:
Update sprint-status.yaml with corrected values Re-parse the file with corrected statusesDetect risks:
/bmad:bmm:workflows:code-review/bmad:bmm:workflows:create-storygenerated timestamp is more than 7 days old: warn "sprint-status.yaml may be stale"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)
dev-story for the first in-progress storycode-review for the first review storydev-storycreate-storyretrospectiveworkflow-status to plan next phase
Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate)
Stories: backlog {{count_backlog}}, ready-for-dev {{count_ready}}, in-progress {{count_in_progress}}, review {{count_review}}, done {{count_done}}
Epics: backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}
Next Recommendation: /bmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
{{#if risks}} Risks: {{#each risks}}
Pick an option: 1) Run recommended workflow now 2) Show all stories grouped by status 3) Show raw sprint-status.yaml 4) Exit Choice:
<output>Run `/bmad:bmm:workflows:{{next_workflow_id}}`.
If the command targets a story, set story_key={{next_story_id}} when prompted.
<output>
<action>Display the full contents of {sprint_status_file}</action>
<action>Exit workflow</action>
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
<template-output>is_valid = false</template-output>
<template-output>error = "sprint-status.yaml missing"</template-output>
<template-output>suggestion = "Run sprint-planning to create it"</template-output>
<action>Return</action>
Read and parse {sprint_status_file}
Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location is_valid = false error = "Missing required field(s): {{missing_fields}}" suggestion = "Re-run sprint-planning or add missing fields manually" Return
Verify development_status section exists 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
Validate all status values against known valid statuses:
is_valid = true message = "sprint-status.yaml valid: metadata complete, all statuses recognized"