spec-kit-analyze

To audit spec, plan, and tasks artifacts for consistency, run a cross-artifact analysis against a feature directory to identify coverage gaps, ambiguities, and duplication without modifying any files.

A cross-artifact gap analysis reads spec.md, plan.md, and tasks.md to detect missing coverage, ambiguous language, and duplicates, producing a structured findings report with routing recommendations.

Yes, evaluating governance conflicts requires reading memory/constitution.md for MUST and SHOULD statements to verify that your spec, plan, and tasks align with established project governance.

Yes, you can perform a strictly read-only audit of a feature directory containing spec.md, plan.md, and tasks.md to generate a gap report without applying any edits to your artifacts.

The best way to find coverage gaps and ambiguities is running a read-only audit that cross-references spec.md, plan.md, and tasks.md, outputting a structured findings report with routing recommendations.

The audit produces routing recommendations to direct you to the specific artifacts requiring updates, helping you resolve identified coverage gaps, ambiguities, duplicates, and constitution conflicts efficiently.