validate-story

To validate a story draft, run a 10-step blueprint check covering template completeness, file structure, acceptance criteria, and anti-hallucination safeguards. The process outputs a GO/NO-GO decision, a readiness score, and categorized issues for critical, should-fix, and nice-to-have items.

A go-no-go readiness assessment evaluates story documentation against a 10-step process to determine if it is complete and actionable. It generates a readiness score and a validation report detailing critical, should-fix, and nice-to-have items before development.

Checking acceptance criteria mapping involves cross-referencing the story draft against the defined tasks to flag uncovered gaps. The validation process ensures all acceptance criteria are satisfied by concrete tasks and identifies missing coverage.

Detecting anti-hallucination risks involves cross-referencing the story draft against project architecture and docs. This validation step ensures the story aligns with existing project guidelines and flags potential hallucinations before development.

Story template completeness validation checks for frontmatter, objective, context, acceptance criteria, tasks, dev notes, testing, and file lists. It ensures the drafted Markdown file contains all required sections for an actionable development handoff.

Yes, you can validate file structure and source-tree consistency by applying the 10-step validation process to the story draft. It checks the specified file lists against project guidelines to ensure structural alignment before development.