What problem does it solve? Agile teams lose track of where their sprint stands when status lives in a raw YAML file. This Skill parses sprint-status.yaml, aggregates story and epic counts, surfaces risks like stale data or orphaned stories, and recommends the next BMAD workflow action. ## Core Features & Use Cases - Sprint Summarization: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and lists open action items. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with interactive correction. - Next-Action Recommendation: Selects the next workflow (dev-story, code-review, create-story, or retrospective) based on priority rules, with interactive, data, and validate execution modes. - Use Case: A developer asks "check sprint status" and immediately sees that 3 stories are in review, the status file is 10 days old, and the recommended next step is running code-review on story 2-1. ## Quick Start Ask the assistant to check sprint status and show the current sprint summary with risks and the recommended next workflow.