Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)
<quick_start> Validate cross-artifact consistency and detect breaking changes:
Inputs: spec.md, plan.md, tasks.md Outputs: analysis-report.md </quick_start>
<workflow> <step number="1"> **Check spec-plan consistency**Read spec.md requirements, verify each has corresponding plan component. Flag missing mappings in analysis report.
See references/examples.md for grep commands. </step>
<step number="2"> **Verify task-implementation alignment**Read plan.md components, verify each broken into tasks in tasks.md.
Validate:
Scan for patterns indicating breaking changes:
<step number="4"> **Validate dependencies** <step number="5"> **Generate analysis report** <validation> After analysis, verify: <pitfall name="inconsistent_artifacts"> **❌ Don't**: Assume spec and plan are aligned **✅ Do**: Explicitly validate each spec requirement has corresponding plan component <pitfall name="no_cross_reference"> **❌ Don't**: Skip dependency validation **✅ Do**: Cross-reference all imports, integrations, external dependencies <pitfall name="vague_findings"> **❌ Don't**: Write vague findings like "inconsistencies found" **✅ Do**: Specify exact artifacts, line numbers, and recommended fixes <references> See references/ for: - Cross-artifact consistency matrix - Breaking change detection patterns - Impact assessment rubric - Real-world analysis examples </references>Flag with impact level (Low/Medium/High) using reference rubric. </step>
Cross-reference:
Verify all dependencies documented and accounted for. </step>
Create specs/NNN-slug/analysis-report.md:
# Analysis Report
## Consistency Check
- Spec-Plan: [✓/✗] Description
- Plan-Tasks: [✓/✗] Description
## Breaking Changes
- [High/Medium/Low] Description and impact
## Dependency Validation
- [✓/✗] Dependencies documented
## Recommendations
- Action items to fix inconsistencies
Update state.yaml: analysis.status = completed
</step>
</workflow>
<anti_patterns> <pitfall name="missing_breaking_changes"> ❌ Don't: Assume no breaking changes without scanning ✅ Do: Explicitly check API signatures, database schema, required fields, auth changes
Why: Breaking changes missed in analysis cause production issues post-deployment </pitfall>
Why: Missing mappings lead to incomplete implementation </pitfall>
Why: Undocumented dependencies cause integration failures </pitfall>
Why: Actionable findings enable quick remediation </pitfall> </anti_patterns>
<success_criteria>