speckit-analyze

To audit spec, plan, and task files for inconsistencies, apply an analysis tool to your Spec Kit project directory. It cross-analyzes spec.md, plan.md, and tasks.md to detect missing coverage, conflicting requirements, and terminology drift, producing a structured, severity-ranked report with suggested remediation steps.

Constitution validation checks your project artifacts against defined constitution principles to flag any MUST-level violations as critical. It ensures your generated tasks and plans align strictly with foundational project rules before coding begins.

Mapping requirements to tasks involves cross-referencing spec.md and tasks.md to identify duplications, ambiguities, and underspecified items. The analysis generates a coverage table that highlights gaps and validates alignment with the original specification.

Yes, the spec audit requires a Spec Kit project that includes a .specify directory. The analysis applies to the FEATURE_DIR spec.md, plan.md, and tasks.md files after task generation and before implementation to ensure accurate cross-artifact validation.

You should run a spec, plan, and task consistency analysis immediately after tasks.md is produced and before implementation begins. This early detection prevents implementation surprises and rework by verifying task coverage and confirming constitution alignment.

The best way to find ambiguities in generated task lists is to cross-analyze tasks.md against spec.md and plan.md. This detects underspecified items and terminology drift, outputting a read-only structured analysis report that assigns severity levels and suggests remediation actions.