validate-story

Story template validation checks Markdown-based stories for compliance gaps, anti-hallucination issues, and implementation readiness. The Skill applies 10-step validation across template structure, file organization, testing requirements, and architecture alignment, then outputs a GO/NO-GO decision with a detailed report.

Anti-hallucination verification ensures story requirements don't contradict your documented architecture or existing capabilities. The Skill cross-references story claims against your architecture and docs to flag unfounded assumptions before implementation begins.

The Skill supports three validation modes: full (comprehensive 10-step check), quick (faster validation for iteration), and critical_only (blockers only). Choose based on your stage—full for final pre-implementation review, quick for rapid feedback during drafting.

The report includes validation_passed status, readiness_score, confidence_level, critical_issues list, anti_hallucination_findings, nice_to_have suggestions, and telemetry. You get both a structured report and actionable issue lists for developer agents.

No external dependencies are required. Stories must be Markdown files organized under .claude/stories. The Skill handles template compliance and readiness assessment as-is; no additional setup or tools are needed.

Story validation targets Markdown-based stories stored under .claude/stories following a specific template structure. It is not suitable for non-template formats, stories outside the designated directory, or contexts where template compliance and anti-hallucination checks are not applicable.