speckit-analyze

To check cross-artifact consistency, you can run a non-destructive analysis across spec.md, plan.md, and tasks.md to identify coverage gaps, terminology drift, and conflicting requirements before implementation begins.

Validating functional requirements against task mappings is performed by cross-referencing success criteria in the spec with the task list to pinpoint coverage gaps and ensure full traceability before development starts.

Enforcing constitution compliance involves validating your specification artifacts against the principles defined in project-specific memory/constitution.md to detect any violations prior to the development phase.

You should run a consistency and quality analysis before starting a new feature implementation to verify that all success criteria in the spec are fully covered by tasks, preventing implementation drift.

No, the spec-kit analysis performs a non-destructive cross-artifact evaluation, meaning it reads your project files to identify inconsistencies and coverage gaps without altering the original artifacts.

The best way to prevent terminology drift is to perform automated cross-artifact validation that checks for conflicting requirements and terminology inconsistencies across spec.md, plan.md, and tasks.md.