What problem does it solve? Agile teams lose track of which epics and stories are in backlog, in progress, or done when status lives only in scattered planning documents. This Skill scans your epic markdown files and produces a single structured sprint-status.yaml that reflects the real state of development. ## Core Features & Use Cases - Epic and Story Parsing: Discovers whole or sharded epic documents (epics.md, epic-1.md, etc.) and extracts every epic, story, and retrospective entry with kebab-case keys. - Intelligent Status Detection: Upgrades story status to ready-for-dev when a matching story file exists, and never downgrades existing advanced statuses like done. - Validated YAML Output: Generates a fully commented sprint-status.yaml with a defined state machine (backlog → ready-for-dev → in-progress → review → done) and runs coverage validation against the source epics. - Use Case: After drafting epics for a task management API, run sprint planning to produce a sprint-status.yaml that developers and agents update as stories move through implementation and code review. ## Quick Start Ask the agent to run sprint planning and generate the sprint status file from your epic documents.
