consistency-analysis

To check for inconsistencies across specification documents, perform a read-only cross-document analysis that evaluates requirement coverage, task traceability, data model consistency, and contract alignment to output a structured report with categorized findings and severity levels.

Cross-document traceability analysis is the process of verifying that requirements in spec.md are fully covered by tasks in tasks.md and that data models in data-model.md match API contracts, ensuring end-to-end specification completeness before development.

Detect conflicting information between spec and task documents by running an automated conflict detection analysis that flags contradictory statements, identifies missing traceability links, and categorizes findings by severity level in a structured report.

You need to run a specification consistency and alignment check before starting development to ensure all requirements in spec.md are covered by tasks in tasks.md, and that plans, data models, and contracts are perfectly aligned and complete.

A gap analysis evaluates documents against eight rule categories: requirement coverage, task traceability, plan alignment, data model consistency, contract coverage, constitution compliance, duplication detection, and ambiguity detection.

No, consistency analysis performs a read-only cross-document analysis that outputs a structured report with categorized findings and severity levels, ensuring your original specification documents remain unmodified during the review process.