story-readiness

To check if a story is ready for implementation, validate its GDD references, ADR acceptance, TR-ID activity, manifest currency, scope boundaries, asset references, and a minimum of three testable acceptance criteria. The evaluation outputs a READY, NEEDS WORK, or BLOCKED verdict with explicit gaps.

Story readiness validation is the process of verifying a story file has complete design documentation, accepted ADRs, active TR-IDs, current manifests, and at least three testable acceptance criteria before implementation begins. It produces READY, NEEDS WORK, or BLOCKED statuses with identified gaps.

Yes, you can validate sprint scope or perform epic-level checks. The validation process applies to single story files, sprint scope validations, and epic-wide checks by loading GDD, control-manifest, TR registry, and ADR statuses to inform readiness decisions across multiple stories.

A story file returns NEEDS WORK or BLOCKED when validation identifies missing design completeness, unaccepted ADRs, inactive TR-IDs, outdated manifests, undefined scope boundaries, missing asset references, or fewer than three testable acceptance criteria. The output explicitly lists these gaps for resolution.

Yes, ADRs and GDD references are required to pass readiness checks. The validation enforces design completeness and ADR acceptance alongside TR-ID activity, manifest currency, scope boundaries, asset references, and a minimum of three testable acceptance criteria to determine a READY verdict.

The minimum number of testable acceptance criteria required for a story to be considered ready is three. The validation enforces this threshold alongside checks for GDD references, ADR status, TR-ID validity, manifest currency, engine notes, and asset references.