validate-story

Validate Markdown stories for template compliance and implementation readiness.

2|2|Updated Oct 28, 2025

Search Tags:#template #architecture #validation #story #GO/NO-GO #anti-hallucination

Ready to run

npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill validate-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-story
Source: https://github.com/adolfoaranaes12/BMAD-ENHANCED/tree/main/.claude/skills/validate-story
Command: npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill validate-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Pre-implementation story validation ensuring templates compliance, anti-hallucination checks, and implementation readiness scoring.

Core Features & Use Cases

10-step validation covering template, file structure, testing, anti-hallucination, GO/NO-GO, and reporting
Anti-hallucination findings checked against architecture and docs
Validation report generation

Quick Start

Example: @validate-story .claude/stories/epic-001/story-003.md

Frequently Asked Questions about validate-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate a story template before implementation?▼

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.

What is anti-hallucination verification and why does it matter in story validation?▼

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.

Can I run validation in quick mode or do I need the full 10-step check?▼

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.

What output does the validation report include?▼

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.

Do I need specific tools or dependencies to use story validation?▼

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.

When should I NOT use story validation?▼

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.