What problem does it solve?
This Skill removes the manual effort of turning epic documents into a usable sprint tracking file. It helps teams create a complete sprint-status.yaml that reflects every epic, every story, and each retrospective entry in a consistent order.
Core Features & Use Cases
- Epic and story inventory generation: Scans planning documents to extract all epics and stories, then converts them into structured status keys.
- Status bootstrap and preservation: Detects whether story files already exist to mark items as ready-for-dev, while preserving more advanced statuses from an existing tracking file.
- Validation for completeness: Checks that no epics or stories are missing, no unexpected items are added, and all entries follow the expected workflow states.
- Use case: A product or engineering team with epic markdown files can use this Skill to generate or refresh a sprint tracking file before planning, execution, or status review.
Quick Start
Run sprint planning to generate or refresh sprint-status.yaml from the current epic files.