speckit-analyze

Cross-artifact inconsistency analysis detects duplication, ambiguity, and coverage gaps across spec.md, plan.md, and tasks.md. It generates a structured report with priority mappings and optional remediation guidance, ensuring project documentation quality before implementation without modifying source artifacts.

You need cross-artifact consistency analysis after task generation and before implementation begins. It validates the spec-kit project structure, including the .specify directory and constitution, to surface any documentation inconsistencies, gaps, or duplication early in the development lifecycle.

No, the consistency analysis does not modify source artifacts like spec.md, plan.md, or tasks.md. It operates strictly as a read-only diagnostic tool that generates a structured report with priority mappings and optional remediation guidance, leaving original documentation files untouched.

The best way to find coverage gaps in a spec-kit project structure is cross-artifact analysis. It identifies missing requirements, duplication, and ambiguity across spec.md, plan.md, and tasks.md, outputting a structured report with priority mappings to resolve documentation issues systematically.

Yes, you can extend cross-artifact analysis for a specific speckit constitution. The analysis supports optional extensions via hook extensions and constitution configurations, allowing you to tailor inconsistency detection, coverage checks, and remediation guidance to fit specific project requirements.