Spec Validation

Systematic quality validation for specifications using structured checklists and self-evaluation patterns.

When to Use

• After drafting *_FEATURE.md specifications
• Reviewing PRDs for completeness
• Validating requirements before handoff
• Self-checking document quality

Core Principle

The best form of feedback is clearly defined rules, then explaining which rules failed and why.

Validation Framework

1. Completeness Check

2. Clarity Check

3. Consistency Check

4. Feasibility Check

Self-Evaluation Pattern

Use mcpsequential-thinkingsequentialthinking for systematic review:

# Structured self-evaluation
mcp__sequential-thinking__sequentialthinking(
    thought="Reviewing spec for completeness: checking problem statement",
    thoughtNumber=1,
    totalThoughts=5,
    nextThoughtNeeded=True
)

Sequential Review Steps

1. Problem Clarity: Is the root problem specific and measurable?
2. User Definition: Are primary users and stakeholders identified?
3. Scope Boundaries: Are in-scope and non-goals explicit?
4. Success Criteria: Can we objectively measure success?
5. Risk Coverage: Are failure scenarios and rollback documented?

Validation Report Template

## Spec Validation Report: {FEATURE_NAME}

### Summary
- **Overall Status**: PASS / NEEDS REVISION
- **Critical Issues**: {count}
- **Warnings**: {count}

### Completeness (X/5 sections)
| Section | Status | Issue |
|---------|--------|-------|
| Problem | PASS/FAIL | {detail if fail} |
| Users | PASS/FAIL | {detail if fail} |
| Scope | PASS/FAIL | {detail if fail} |
| Success | PASS/FAIL | {detail if fail} |
| Risks | PASS/FAIL | {detail if fail} |

### Clarity Issues
- [ ] {Issue 1}
- [ ] {Issue 2}

### Consistency Issues
- [ ] {Contradiction 1}

### Open Questions (Require Stakeholder Input)
1. {Question needing clarification}

### Recommendations
1. {Specific fix recommendation}

Common Validation Failures

Integration Points

After requirements-discovery

Discovery Interview Complete
    -> Draft *_FEATURE.md
    -> spec-validation (this skill)
    -> Identify gaps
    -> Follow-up questions
    -> Final draft

Before implementation

*_FEATURE.md Finalized
    -> spec-validation final check
    -> Engineering review
    -> Implementation begins

Quick Checklist (Copy/Paste)

### Pre-Finalization Checklist
- [ ] Problem is specific, not vague
- [ ] Success metrics are quantified
- [ ] Non-goals are explicitly stated
- [ ] No TBD/TODO items remain
- [ ] Acronyms defined
- [ ] Edge cases documented
- [ ] Error messages are user-actionable
- [ ] No policy contradictions
- [ ] Trade-offs explicitly documented
- [ ] Priorities clear (must-have vs nice-to-have)
- [ ] Technical constraints validated
- [ ] Dependencies identified
- [ ] Risks have mitigation plans