What problem does it solve? Teams using file-based agile planning lose track of which epics and stories are backlog, in-progress, or done because status lives scattered across markdown files. This Skill consolidates epic documents into a single structured sprint-status.yaml that reflects current development state. ## Core Features & Use Cases - Epic and Story Parsing: Scans epic markdown files (whole or sharded) and extracts every epic, story, and retrospective entry into kebab-case keys. - Intelligent Status Detection: Upgrades story status to ready-for-dev when a matching story file exists, and preserves more advanced existing statuses without downgrading. - Validation and Reporting: Verifies complete coverage of epics and stories, checks YAML validity, and reports totals for epics, stories, and completed work. - Use Case: After writing epics for a new project, run sprint planning to produce a sprint-status.yaml that developers and agents update as stories move from backlog through review to done. ## Quick Start Run sprint planning to generate the sprint status file from my epic documents.
