What problem does it solve? Agile teams using the BMAD method lose visibility into which stories and epics are in progress, blocked, or done, and often don't know which workflow to run next. This Skill reads the sprint-status.yaml tracking file and turns it into a clear status summary with risk warnings and a concrete next-step recommendation. ## Core Features & Use Cases - Sprint Status Summary: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and displays a formatted overview. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values, with interactive correction of invalid entries. - Next Workflow Recommendation: Selects the next BMAD workflow (dev-story, code-review, create-story, or retrospective) based on priority rules over the current sprint state. - Use Case: A developer starts their day and asks for the sprint status; the Skill reports that story 2-3 is in review, warns the file is 8 days stale, and recommends running the code-review workflow. ## Quick Start Ask the assistant to check the sprint status and it will load sprint-status.yaml, summarize progress, and recommend the next workflow.
