What problem does it solve? Agile teams using file-based planning lose track of which epics and stories are backlog, in-progress, or done. This Skill automates the creation and maintenance of a sprint-status.yaml file so sprint tracking stays synchronized with the actual epic documents and story files on disk. ## Core Features & Use Cases - Epic and Story Parsing: Scans epic markdown files (whole or sharded) and extracts every epic, story, and retrospective entry with kebab-case keys. - Intelligent Status Detection: Upgrades stories to ready-for-dev when story files exist, preserves more advanced existing statuses, and never downgrades progress. - Validated YAML Output: Produces a structured sprint-status.yaml with documented status state machines, ordered entries, and carried-over retrospective action items. - Use Case: After writing epics for a new product, run sprint planning to instantly generate a complete tracking file that developers and agents update as work progresses. ## Quick Start Ask the AI to run sprint planning and generate the sprint status file from your epic documents.