story-readiness

To check story readiness, validate embedded CDD requirements, ADR references, and acceptance criteria. This process surfaces missing references and unresolved questions, returning a READY, NEEDS WORK, or BLOCKED verdict with explicit gaps before development begins.

Story readiness validation ensures a story file has traceable CDD requirements, ADR references, and clear acceptance criteria before implementation. You need it to identify scoping gaps and unresolved questions early, returning a READY, NEEDS WORK, or BLOCKED verdict with actionable fixes.

Yes, you can validate acceptance criteria across individual stories, sprint-level selections, or entire epic collections. The check processes all selected story files to surface missing ADR references or unresolved CDD requirements, returning a verdict for each.

To ensure acceptance criteria are testable and properly scoped, run a readiness check against the story file. This validates that the criteria are clear and properly bounded, returning a NEEDS WORK or BLOCKED verdict with explicit gaps if scoping is insufficient.

The best way to trace ADR references and CDD requirements is to apply a readiness gate to the stories. This validates that embedded references are traceable and complete, returning a READY verdict or listing explicit gaps and suggested fixes.

A story readiness check returns a BLOCKED verdict when critical implementation prerequisites are missing. The validation explicitly identifies unresolved questions, missing ADR references, or untraceable CDD requirements, providing notes on what must be resolved before work begins.