story-readiness

To check if a story is implementation-ready, validate its embedded GDD requirements, ADR references, engine notes, and acceptance criteria. This verifies machine-checkable items like TR-ID validity and manifest version, returning a READY, NEEDS WORK, or BLOCKED verdict with specific gaps.

Story readiness validation is the process of verifying a backlog story has clear GDD references, valid ADR status, and no open design questions before sprint planning. It outputs a structured verdict and explicit remediation guidance for any non-ready stories.

Validate ADR references and TR-ID status by loading reference registries and checking them against the story file. This confirms ADR status, TR-ID validity, and manifest version, flagging outdated manifest rules when present to ensure the story is implementation-ready.

You can verify readiness for an entire sprint or all stories in production by loading reference documents once. The validation applies to individual stories or entire scopes, reporting a per-story verdict with concrete gaps for any stories that need work.

A BLOCKED story readiness verdict means the story lacks critical implementation prerequisites like GDD requirements, valid ADR references, or clear acceptance criteria. The validation provides a structured verdict with explicit remediation guidance to resolve the identified gaps.

Your story file fails readiness checks for missing GDD requirements if it lacks a design/gdd/ path or does not quote a specific requirement from that GDD. The validator requires a specific rule reference, not just the GDD filename, to pass.