What problem does it solve? Agile teams lose track of where stories and epics stand across a sprint. This Skill reads the sprint-status.yaml tracking file, aggregates story, epic, and retrospective counts, surfaces risks like stale data or orphaned stories, and recommends the next workflow to run. ## Core Features & Use Cases - Sprint Aggregation: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and validates all status values against known states. - Risk Detection: Flags stale status files older than 7 days, orphaned stories without a matching epic, in-progress epics with no stories, and unknown status values with interactive correction. - Next-Action Recommendation: Selects the next workflow (dev-story, code-review, create-story, or retrospective) with the target story and agent role, and supports data and validate modes for programmatic consumption. - Use Case: A developer starts the day by asking for sprint status, sees that one story is in review and two are ready for development, and immediately launches the recommended code-review workflow. ## Quick Start Ask the assistant to check sprint status and show the recommended next workflow for the current project.