speckit-analyze

To check consistency between requirements, plans, and tasks, analyze your spec.md, plan.md, and tasks.md files to identify coverage gaps, ambiguity, and constitution violations. This cross-artifact validation ensures every requirement maps directly to a task, preventing implementation drift.

Cross-artifact validation in software documentation detects mismatches between requirements, technical plans, and assigned tasks. It confirms that functional requirements in your spec are fully accounted for in your task list and ensures technical alignment before development begins.

To validate requirement-to-task mapping for a new sprint, run a cross-artifact analysis on your Spec Kit directory. This verifies that every functional requirement in your spec is accounted for in your task list and that no tasks reference undefined components.

Yes, Spec Kit enforces project constitution and quality gates across artifacts. The analysis ensures all project files strictly adhere to your defined rules, identifying constitution violations and technical misalignments before implementation begins.

You need to run a documentation consistency analysis before starting a new sprint or implementation phase. This identifies inconsistencies, ambiguities, and coverage gaps across your core documentation to ensure technical alignment and prevent implementation drift.

The limitation of non-destructive documentation analysis is that it only identifies inconsistencies, ambiguities, and coverage gaps without automatically modifying your spec.md, plan.md, or tasks.md files. You must manually resolve the flagged constitution violations and mapping errors.