speckit.analyze

Cross-document consistency checking compares spec.md, plan.md, and tasks.md to identify duplicates, ambiguities, and specification compliance issues. It performs read-only analysis across project artifacts and outputs a concise Markdown report detailing discrepancies without modifying your files.

Non-destructive specification compliance analysis is a read-only process that scans project documentation to catch inconsistencies and underspecified parts early. It prevents modifications to your files while providing a user-friendly report that suggests fixes for critical issues.

No, the consistency check performs non-destructive analysis, meaning it is strictly read-only and prevents modifications to your files. It safely identifies discrepancies across spec.md, plan.md, and tasks.md and outputs findings in a separate Markdown report.

You need to run a specification compliance check after generating project tasks and plans, as converting ideas into documented artifacts often introduces inconsistencies. Running it early in the workflow catches discrepancies across spec.md, plan.md, and tasks.md before development.

Yes, you can invoke automated remediation suggestions after the consistency report is completed. This optional feature provides concrete recommendations to resolve critical inconsistencies and ambiguities found within your project documentation.

Yes, the specify dependency is required to perform cross-document quality checks using pre-configured scripts. It provides the foundational environment needed to compare your spec.md, plan.md, and tasks.md files for constitution compliance.