What problem does it solve? It closes the gap between planning artifacts and implementation by checking that epics and stories are complete enough to build, then generating and maintaining a sprint-status.yaml file that tracks every epic, story, and retrospective through the development lifecycle. ## Core Features & Use Cases - Readiness Gate: Audits planning artifacts (PRDs, architecture, epics) and returns a PASS, CONCERNS, or FAIL verdict before any code is written. - Deterministic Tracking Generation: Parses epic files into kebab-case keys, merges with existing statuses without downgrades, and writes sprint-status.yaml atomically via a Python script. - Status, Validate, and Repair: Summarizes sprint progress with risks and next recommended actions, validates file structure, and rebuilds broken tracking files from evidence with user confirmation. - Use Case: After finishing your epics, ask the assistant to run sprint planning; it checks implementability, generates the tracking file, 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 your epics.