What problem does it solve? Agile teams lose track of which epics and stories are done, in progress, or blocked when sprint state lives only in chat history or scattered notes. This Skill checks whether your planning artifacts are complete enough to implement, then generates and maintains a structured sprint-status.yaml file that tracks every epic, story, and retrospective. ## Core Features & Use Cases - Readiness Gate: Audits briefs, PRDs, architecture docs, and epics to confirm a developer could implement the plan without inventing unrecorded decisions, returning a PASS, CONCERNS, or FAIL verdict. - Deterministic Tracking Generation: Parses epic files into kebab-case story keys and writes sprint-status.yaml via a Python script with atomic writes, status preservation, and legacy v6 status normalization. - Status, Validate, and Fix Flows: Summarizes sprint progress with risks and next recommended actions, validates the tracking file's structure, and rebuilds broken files through evidence-gathering and user confirmation. - Use Case: After writing epics for a new feature, ask the assistant to run sprint planning; it verifies readiness, generates sprint-status.yaml, and later tells you which story to build next. ## Quick Start Ask the assistant to run sprint planning and generate the sprint status file from the epics in your planning docs folder.
