What problem does it solve? Agile teams need a reliable way to know whether their planning artifacts are complete enough to build from, and a single source of truth for tracking epic and story progress. This Skill checks implementation readiness, then generates and maintains a sprint-status.yaml file that stays in sync with your epic documents. ## Core Features & Use Cases - Readiness Gate: Audits briefs, PRDs, architecture, and epics against one question — could a developer implement these stories without inventing unrecorded decisions — and returns a PASS, CONCERNS, or FAIL verdict. - Deterministic Tracking Generation: Parses epic files into kebab-case story keys, merges with existing statuses without downgrades, detects story files on disk, and writes sprint-status.yaml atomically with post-write validation. - Status, Validate, and Repair: Summarizes sprint progress with risks and next recommended actions, validates tracking file structure, and rebuilds broken files through evidence-gathering and user confirmation. - Use Case: After finishing your PRD and epics, ask the agent to run sprint planning; it flags a story with no recorded architecture decision, you fix it, and it generates a sprint-status.yaml ready for the build workflow. ## Quick Start Ask the agent to run sprint planning and generate the sprint status file from your epics.
