story-readiness

To check story readiness, validate the story file against a multi-part checklist covering GDD references, ADR status, TR-IDs, acceptance criteria, and asset existence. This produces a READY, NEEDS WORK, or BLOCKED verdict with precise gap descriptions to prevent mid-sprint design interruptions.

ADR status validation for sprint planning ensures that referenced Architecture Decision Records are accepted and aligned with the control manifest. This cross-reference prevents developers from starting implementation on stories blocked by unresolved architectural decisions or manifest mismatches.

Validate acceptance criteria testability by scanning all story files in the current sprint directory to ensure criteria are met and traceable. The readiness check returns a detailed gap list for any story failing testability requirements, producing deterministic NEEDS WORK or BLOCKED verdicts.

Yes, you can check GDD references and asset existence across all production epics by running the readiness validation on the entire production directory. It cross-references cached design entries and scans asset paths to ensure all referenced assets exist before generating comprehensive verdicts.

Story readiness validation strictly preserves read-only operation and does not modify any repository files. It only reads and cross-references GDD entries, ADR statuses, control manifests, TR registries, sprint priorities, and asset paths to produce deterministic verdicts and gap lists.

Verifying TR-ID validity before development ensures that traceability identifiers in your story files match entries in the TR registry. This prevents implementation gaps by confirming that every story is properly linked to registered technical requirements before work begins.