story-readiness

To check story readiness, validate the story file for clear acceptance criteria, scope boundaries, dependency checks, and test evidence. This returns a READY, NEEDS WORK, or BLOCKED verdict with specific missing requirements to resolve before implementation begins.

Story readiness validation is the process of verifying drafted stories have complete requirements before development begins. It matters because catching gaps early reduces mid-sprint design churn, missing requirements, and costly rework during the active sprint cycle.

You can validate acceptance criteria and traceability by running a readiness review across single-story, sprint, or all-story scopes. This checks CDD traceability, ADR status, TR-ID validity, and manifest version alignment to flag gaps across batches.

Yes, you can run readiness triage on stories with open dependencies and blocking questions. The validation checks dependency status and flags unresolved open questions that would block development, returning a NEEDS WORK or BLOCKED status.

Architecture and governance checks needed before implementation include verifying CDD traceability, ADR status, TR-ID validity, and manifest version alignment. These checks ensure the story aligns with architectural decisions and governance requirements.

A story receives a BLOCKED verdict during pre-sprint review when validation identifies missing requirements like unclear acceptance criteria, unresolved dependencies, invalid TR-IDs, or blocking open questions that prevent development from starting.