Audits specification files for quality against a rubric covering structure, requirements, acceptance criteria, traceability, and quality; generates A-F graded reports with issues and recommendations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spec-driven-development:auditThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Perform a comprehensive quality audit of specifications with formal scoring.
Perform a comprehensive quality audit of specifications with formal scoring.
Load Specifications
--all flag, audit all specifications in .specs/Execute Audit
spec-reviewer audit agentGenerate Report
$ARGUMENTS - Path to specification file--all - Audit all specifications--format - Output format: markdown (default), json# Audit single specification
/spec-driven-development:audit .specs/user-auth/spec.md
# Audit all specifications
/spec-driven-development:audit --all
# JSON output for tooling
/spec-driven-development:audit .specs/user-auth/spec.md --format json
| Category | Weight | Criteria |
|---|---|---|
| Structure | 20% | Required sections, frontmatter, organization |
| Requirements | 25% | EARS format, completeness, clarity |
| Acceptance Criteria | 25% | Given/When/Then, coverage, testability |
| Traceability | 15% | IDs, cross-references, dependencies |
| Quality | 15% | INVEST scores, no ambiguity, specificity |
| Grade | Score | Status |
|---|---|---|
| A+ | 95-100 | Exceptional |
| A | 90-94 | Excellent |
| B | 80-89 | Good |
| C | 70-79 | Acceptable |
| D | 60-69 | Needs Work |
| F | <60 | Failing |
# Specification Audit Report
**Specification:** user-auth
**Audited:** 2024-01-15T10:30:00Z
**Grade:** B (84/100)
## Category Scores
| Category | Score | Max | % |
| --- | --- | --- | --- |
| Structure | 18 | 20 | 90% |
| Requirements | 21 | 25 | 84% |
| Acceptance Criteria | 20 | 25 | 80% |
| Traceability | 13 | 15 | 87% |
| Quality | 12 | 15 | 80% |
| **TOTAL** | **84** | **100** | **84%** |
## Issues Found
### Critical (0)
None
### Major (2)
1. **FR-3:** Missing acceptance criteria for error case
2. **NFR-1:** Performance threshold not testable
### Minor (3)
1. **FR-1.AC-2:** Could be more specific
2. **FR-2:** Consider splitting into smaller requirements
3. **Dependencies:** Missing link to FR-1
## Recommendations
1. Add acceptance criteria for FR-3 error handling
2. Specify measurable threshold for NFR-1
3. Consider refining FR-2 for better INVEST score
## Comparison (if previous audit exists)
| Metric | Previous | Current | Change |
| --- | --- | --- | --- |
| Grade | C (75) | B (84) | +9 |
| Issues | 8 | 5 | -3 |
/spec-driven-development:validate - Quick validation check/spec-driven-development:refine - AI-assisted improvements/spec-driven-development:status - View specification statusnpx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentAudits SPEC documents with declarative structural checks and content review, producing a combined report for doc-spec-fixer. Use for quality gating before TDD generation.
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.
Reviews spec.md files for completeness, clarity, implementability, testability, and structure. Identifies ambiguities, gaps, and missing sections before implementation.