speckit-analyze

Cross-artifact consistency analysis evaluates spec.md, plan.md, and tasks.md to identify terminology drift and conflicting requirements before implementation. It non-destructively scans your project documentation to ensure alignment and readiness.

Coverage validation detects requirements without associated tasks and tasks missing clear specifications. By cross-referencing spec.md and tasks.md, it highlights missing connections to ensure full requirement traceability.

Yes, consistency analysis requires a valid spec-kit project structure with a .specify directory. This directory is necessary for the validation logic to execute and evaluate your project documentation.

Constitution enforcement automatically flags violations of project-specific principles defined within your documentation. It checks spec.md and plan.md against these foundational rules to maintain architectural alignment.

Yes, the consistency and quality analysis process is non-destructive. It evaluates your project documentation for ambiguities and coverage gaps without altering the original specification or task files.

Terminology drift is flagged during consistency analysis when conflicting terms or requirements appear across spec.md, plan.md, and tasks.md. Identifying these discrepancies early prevents implementation errors.