story-readiness

Validate game development stories by checking for GDD requirements, ADR references, and clear acceptance criteria. This process eliminates ambiguity and reduces the risk of mid-sprint design interruptions before implementation begins.

Story validation is the process of verifying that narrative design, system design, and feature stories have all necessary requirements met before implementation. It ensures completeness by checking game design documents and architecture review documents.

Yes, you can validate all production stories in a single batch. The story validation scope is flexible, allowing you to target specific story files, all stories in a sprint, or all production stories simultaneously.

Before implementing a game feature story, you need to check for GDD requirements, ADR references, engine notes, clear acceptance criteria, and ensure there are no open design questions. Access to game design documents is required.

A story readiness check identifies blocked game development tasks by outputting a verdict of READY, NEEDS WORK, or BLOCKED. It highlights specific gaps in the story file, such as missing ADR references or open design questions.