bmad-sprint-status

Summarizes sprint-status.yaml and recommends the next BMAD workflow action.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-sprint-status-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/4-implementation/bmad-sprint-status
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-sprint-status-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams using the BMAD method lose track of story and epic progress scattered across sprint-status.yaml files, making it hard to spot risks and decide which workflow to run next. ## Core Features & Use Cases - Sprint Summary: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and displays a consolidated report. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and invalid status values, with interactive correction prompts. - Next-Action Recommendation: Selects the next workflow (dev-story, code-review, create-story, or retrospective) based on priority rules, and supports data and validate modes for other flows. - Use Case: A developer returning to a project asks for sprint status and immediately sees that one story is in review, receives a recommendation to run code-review, and gets warned that the status file is over 7 days old. ## Quick Start Ask the agent to check sprint status and show the recommended next workflow for the current project.

Frequently Asked Questions about bmad-sprint-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check sprint status in a BMAD project?▼

Run the sprint-status workflow, which reads the sprint-status.yaml file under your implementation artifacts directory. It displays story and epic counts by status, open action items, detected risks, and a recommended next workflow.

What happens if sprint-status.yaml is missing?▼

The workflow exits with a message telling you to run the sprint-planning workflow first to generate the file. In validate mode it returns is_valid=false with a suggestion to run sprint-planning.

How does the skill decide which workflow to recommend next?▼

It follows a priority order: in-progress stories trigger dev-story, review stories trigger code-review, ready-for-dev stories trigger dev-story, backlog stories trigger create-story, and optional retrospectives trigger retrospective.

Can invalid status values in sprint-status.yaml be fixed automatically?▼

The workflow lists unrecognized statuses and prompts you to enter corrections interactively, then updates the file and re-parses it. You can also skip corrections and continue without fixing.

What risks does sprint status detection surface?▼

It warns when the status file is over 7 days old, when stories are orphaned from epics, when in-progress epics have no stories, and when stories sit in review or in-progress without follow-up work ready.