What problem does it solve? Agile teams tracking epics and stories in a sprint-status.yaml file lack a quick way to see overall progress, detect stale or inconsistent data, and decide which workflow to run next. This Skill parses the status file, validates every status value, surfaces risks, and recommends the next action. ## Core Features & Use Cases - Sprint Summary: Counts stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and displays a formatted dashboard. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with interactive correction. - Next-Action Recommendation: Prioritizes the next workflow (dev-story, code-review, create-story, or retrospective) based on current statuses. - Use Case: A developer returning to a project asks for sprint status and immediately sees that two stories are in review, the file is 10 days stale, 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.