speckit-analyze

To check consistency across spec, plan, and tasks documents, run a non-destructive quality analysis on your spec-kit artifacts. This identifies duplications, ambiguities, and underspecified items across your project documentation.

Yes, you need a spec-kit project structure with a .specify/ directory to analyze project artifacts. The consistency check requires this specific environment setup to parse your spec.md, plan.md, and tasks.md files.

You should run a quality assurance check on project documentation immediately after task generation. This post-generation analysis identifies inconsistencies and underspecified items before development begins.

Non-destructive analysis for project artifacts is a consistency check that reviews spec.md, plan.md, and tasks.md without modifying them. It surfaces ambiguities and duplications to ensure cross-artifact quality.

The best way to find underspecified items in a spec-kit project is to perform a cross-artifact consistency analysis. This detects ambiguities and gaps across your spec.md, plan.md, and tasks.md files.

Yes, you can use this consistency check to find duplications in tasks.md. The analysis scans spec.md, plan.md, and tasks.md to detect duplications, inconsistencies, and underspecified items across all project artifacts.