story-readiness

To validate implementation readiness, check that game development story files contain referenced GDD requirements, accepted ADRs, and testable acceptance criteria. Running this validation during sprint planning produces explicit READY, NEEDS WORK, or BLOCKED verdicts with actionable gap lists.

Story readiness validation is a comprehensive checklist process ensuring game dev stories contain complete implementation context. It verifies design completeness, architecture alignment, scope clarity, and definition of done requirements across 10+ checklist items before developers begin work.

Yes, you can check all stories in a current game dev sprint for missing requirements. The validation supports flexible scope, allowing you to validate a single story file, all current sprint stories, or every story across all production epics for missing GDD references and ADRs.

A game development story receives a BLOCKED status during readiness checks when it lacks critical implementation context such as unresolved design questions, missing GDD compliance, or dependency issues. The validation produces explicit verdicts with specific, fixable gap descriptions to resolve these blockers.

Yes, story readiness validation explicitly checks for GDD compliance and ADR approvals. It validates that story files contain all referenced Game Design Document requirements and approved Architectural Decision Records, ensuring architecture alignment and design completeness before sprint assignment.