What problem does it solve? Agile teams lose track of where stories and epics stand when sprint data lives in a raw YAML file. This Skill parses sprint-status.yaml, counts story and epic statuses, surfaces risks like stale data or orphaned stories, and recommends the next 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 displays a formatted summary. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with guided 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 story counts, risks, and a recommendation to run code review on the story currently in review. ## Quick Start Ask the assistant to check the sprint status and show the recommended next workflow for the current project.