analyze

A read-only consistency audit compares spec.md, plan.md, and tasks.md to identify duplication, ambiguity, terminology drift, and coverage gaps. It generates a deterministic Markdown report detailing findings and constitutional alignment without modifying any source files.

You need a specification consistency check after finishing your tasks breakdown and before starting implementation. This timing verifies coherence across your planning artifacts, catching constitutional misalignments and coverage gaps early when they are least expensive to resolve.

Yes, you can check alignment without modifications by using a strictly read-only audit workflow. It analyzes the existing documents and outputs a structured Markdown report with stable IDs for reproducible reviews, ensuring your spec.md, plan.md, and tasks.md remain untouched.

Terminology drift occurs when inconsistent vocabulary is used across specification, planning, and task documents. A spec audit detects this by cross-referencing the text in spec.md, plan.md, and tasks.md, flagging ambiguous terms and inconsistencies in a structured findings report.

Yes, the documentation audit strictly requires spec.md, plan.md, and tasks.md files to exist. The analysis cross-references all three artifacts to identify coverage gaps and constitutional misalignments, meaning it cannot run if any prerequisite file is missing.

The best way to verify constitution alignment is to run a deterministic audit comparing your specifications against constitutional rules. This generates a structured Markdown report with stable IDs, highlighting misalignments and coverage gaps for review before you begin implementation.