story-readiness

To verify user stories for implementation readiness, validate design references, ADR cross-references, acceptance criteria, manifest versions, asset existence, estimates, and dependencies. This produces per-story verdicts of READY, NEEDS WORK, or BLOCKED with detailed gap reports to prevent mid-sprint interruptions.

Story readiness validation checks that user stories contain all required design, architecture, testing, and asset information. It solves the problem of developer guesswork and mid-sprint surprises by confirming implementation can begin without interruptions, producing detailed gap lists for missing elements.

Checking asset existence uses globbing to confirm referenced assets are present and flags missing files. Manifest version consistency is validated alongside ADR status and TR-ID registry lookups during the readiness check, ensuring all cross-references and dependencies are resolved before implementation.

Yes, aggregate and sprint modes allow validating a single story, all stories in a sprint, or every story in production using an all-stories glob. Each mode emits per-story verdicts with detailed gap lists, enabling batch verification across the entire project backlog.

Unresolved questions and missing sections are reported as gaps in the readiness verdict. The read-only reporting suggests fixes and offers to draft missing sections conversationally without writing files, maintaining a safe review process while highlighting what needs attention.

Director gate integration respects review modes including solo, lean, and full, spawning QA review tasks when required. Sprint escalation warnings are produced for blocked stories, ensuring proper workflow gates are enforced before implementation begins.