story-readiness

Run a story readiness validation to check if your user story files contain all required implementation context, including GDD requirements, ADR references, and testable acceptance criteria. This prevents mid-sprint blockers by verifying completeness across design, architecture, and scope fields before development begins.

Mid-sprint blockers typically occur when user stories lack critical implementation context like referenced GDD requirements, accepted ADRs, or testable acceptance criteria. Validating story readiness before assigning work prevents the rework and unplanned design work that causes these delays.

You can validate user stories across single files, full sprints, or all epic story collections within the Overdrive project structure. The process checks each story against design, architecture, scope, and definition of done rules, producing READY, NEEDS WORK, or BLOCKED verdicts for the entire batch.

Testable acceptance criteria provide specific, measurable implementation targets, such as "jump reaches 5 units height in 0.3 seconds." Story readiness validation enforces that these criteria are present and clearly defined to prevent ambiguous development expectations during the sprint.

Yes, story readiness validation is specifically designed for game development workflows using the Overdrive project structure. It checks story files within the production epics directory to enforce completeness rules across design, architecture, scope, and definition of done fields.

When a user story is missing ADR references, the validation returns a NEEDS WORK or BLOCKED verdict with specific descriptions of the missing items and exact fixes required. You must resolve these gaps by adding the accepted architecture decision records before assigning the story.