gds-sprint-status

name	gds-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.

Paths

• sprint_status_file = {implementation_artifacts}/sprint-status.yaml

Input Files

Input	Path	Load Strategy
Sprint status	{sprint_status_file}	FULL_LOAD

Context

• project_context = **/project-context.md (load if exists)

---

Conventions

• Bare paths (e.g. template.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:

1. {skill-root}/customize.toml — defaults
2. {project-root}/_bmad/custom/{skill-name}.toml — team overrides
3. {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.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Config

Load config from {project-root}/_bmad/gds/config.yaml and resolve:

• user_name
• communication_language
• implementation_artifacts

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation is complete. Begin the workflow below.

EXECUTION

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:gds: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

Validate all statuses against known values:

• Valid story statuses: backlog, ready-for-dev, in-progress, review, done, drafted (legacy)

• Valid epic statuses: backlog, in-progress, done, contexted (legacy)

• Valid retrospective statuses: optional, done

⚠️ Unknown status detected: {{#each invalid_entries}}

• {{key}}: "{{status}}" (not recognized) {{/each}}

Valid statuses:

• Stories: backlog, ready-for-dev, in-progress, review, done
• Epics: backlog, in-progress, done
• Retrospectives: optional, done How should these be corrected? {{#each invalid_entries}} {{@index}}. {{key}}: "{{status}}" → [select valid status] {{/each}}

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 statuses

Detect risks:

• IF any story has status "review": suggest /bmad:gds:workflows:code-review
• IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story
• IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt /bmad:gds:workflows:create-story
• IF last_updated timestamp is more than 7 days old (or last_updated is missing, fall back to generated): warn "sprint-status.yaml may be stale"
• IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected"
• IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories"

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 (next_agent = DEVELOPER) 2. Else if any story status == review → recommend `code-review` for the first review story (next_agent = REVIEWER) 3. Else if any story status == ready-for-dev → recommend `dev-story` (next_agent = DEVELOPER) 4. Else if any story status == backlog → recommend `create-story` (next_agent = STORY_AUTHOR) 5. Else if any retrospective status == optional → recommend `retrospective` (next_agent = FACILITATOR) 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. Note: in the consolidated GDS Phase 4 model, all role labels (DEVELOPER, REVIEWER, STORY_AUTHOR, FACILITATOR) map to the same agent (gds-agent-game-dev / Link Freeman). The labels are kept for downstream consumers that distinguish them semantically. ## 📊 Sprint Status

• Project: {{project}} ({{project_key}})
• Tracking: {{tracking_system}}
• Status file: {sprint_status_file}

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:gds:workflows:{{next_workflow_id}} ({{next_story_id}})

{{#if risks}} Risks: {{#each risks}}

• {{this}} {{/each}} {{/if}}

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:gds: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} Exit workflow

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.

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}} next_agent = {{next_agent}} 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

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.

Check that {sprint_status_file} exists is_valid = false error = "sprint-status.yaml missing" suggestion = "Run sprint-planning to create it" Return

Read and parse {sprint_status_file}

Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location (last_updated is optional for backward compatibility) 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:

• Stories: backlog, ready-for-dev, in-progress, review, done (legacy: drafted)
• Epics: backlog, in-progress, done (legacy: contexted)
• Retrospectives: optional, done is_valid = false error = "Invalid status values: {{invalid_entries}}" suggestion = "Fix invalid statuses in sprint-status.yaml" Return

is_valid = true message = "sprint-status.yaml valid: metadata complete, all statuses recognized" 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.