Validates specification files against schema, EARS patterns, Given/When/Then acceptance criteria, and quality rules with INVEST scores. Reports issues by severity for spec-driven development.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spec-driven-development:validateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate a specification against the canonical schema and quality rules.
Validate a specification against the canonical schema and quality rules.
Load Specification
Schema Validation
spec-reviewer validate agentEARS Pattern Validation
Acceptance Criteria Validation
Quality Assessment
Report Results
$ARGUMENTS - Path to specification file# Validate specific specification
/spec-driven-development:validate .specs/user-auth/spec.md
# Validate all specifications
/spec-driven-development:validate --all
# Validation Report: user-auth
**Status:** ⚠️ PASS WITH WARNINGS
**Timestamp:** 2024-01-15T10:30:00Z
## Schema Compliance
✓ All required fields present
✓ Valid frontmatter format
✓ Requirement IDs follow pattern
## EARS Format
✓ FR-1: Valid Event-Driven pattern
✓ FR-2: Valid State-Driven pattern
⚠️ FR-3: Missing SHALL keyword
## Acceptance Criteria
✓ All requirements have criteria
✓ Given/When/Then format correct
⚠️ FR-2.AC-3: Vague "then" clause
## INVEST Scores
| Req | I | N | V | E | S | T | Total |
| --- | - | - | - | - | - | - | ----- |
| FR-1 | 2 | 2 | 2 | 2 | 2 | 2 | 12/12 |
| FR-2 | 2 | 2 | 2 | 1 | 2 | 1 | 10/12 |
| FR-3 | 2 | 2 | 2 | 2 | 1 | 2 | 11/12 |
## Recommendations
1. FR-3: Add SHALL keyword for EARS compliance
2. FR-2.AC-3: Make outcome more specific
/spec-driven-development:audit - Full quality audit with scoring/spec-driven-development:refine - AI-assisted refinement/spec-driven-development:specify - Generate new specificationnpx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentAudits specification files for quality against a rubric covering structure, requirements, acceptance criteria, traceability, and quality; generates A-F graded reports with issues and recommendations.
Reviews spec.md files for completeness, clarity, implementability, testability, and structure. Identifies ambiguities, gaps, and missing sections before implementation.
Audits SPEC documents with declarative structural checks and content review, producing a combined report for doc-spec-fixer. Use for quality gating before TDD generation.