story-readiness

To check story readiness, validate the story file's design completeness, ADR references, and acceptance criteria against project governance rules. This produces a READY, NEEDS WORK, or BLOCKED verdict with actionable gaps to resolve before development begins.

Story readiness validation is the preflight process of ensuring a story file contains everything a developer needs to begin implementation. It prevents mid-sprint design interruptions by verifying design completeness, dependencies, and unambiguous acceptance criteria.

Yes, you can validate story readiness across a specific story file, an entire epic, or a full sprint scope. The tool parses arguments to scope validation and loads supporting context like manifest rules and ADR statuses once per run.

A NEEDS WORK or BLOCKED verdict indicates the story file has gaps preventing implementation. NEEDS WORK highlights missing design elements or criteria, while BLOCKED tracks unresolved dependencies or missing ADR references that must be addressed first.

Yes, story readiness validation checks ADR statuses and manifest rules as defined in project governance. It loads the ADR registry and GDD references to ensure the story aligns with established architecture decisions before implementation.

To fix gaps found during story readiness preflight checks, address the actionable items listed in the verdict. Update the story file's design completeness, resolve dependency blockers, and ensure all acceptance criteria and ADR references meet manifest rules.