What problem does it solve? Agile teams lose track of which epics and stories are in backlog, in progress, or done when planning artifacts live only in markdown files. This Skill automatically builds a structured sprint-status.yaml from your epic documents so development progress is tracked in one canonical file. ## Core Features & Use Cases - Epic and Story Parsing: Discovers whole or sharded epic markdown files and extracts every epic, story, and retrospective entry. - Intelligent Status Detection: Upgrades story status to ready-for-dev when a matching story file exists, and never downgrades existing statuses. - Validated YAML Output: Generates a sprint-status.yaml with defined status state machines (backlog, in-progress, review, done) and runs completeness checks against the source epics. - Use Case: After writing epics for a new product, ask the agent to run sprint planning and receive a complete sprint-status.yaml listing every epic, story, and retrospective with detected statuses. ## Quick Start Run sprint planning to generate the sprint status file from my epic documents.