speckit-analyze

Cross-artifact consistency checking compares spec.md, plan.md, and tasks.md to detect drift in requirements, terminology, and coverage. It generates a structured, read-only findings report covering duplication, ambiguity, underspecification, and inconsistencies to prevent implementation churn.

Cross-artifact spec analysis is a non-destructive validation process that reads core Spec Kit artifacts within the .specify/ directory structure. It surfaces vague success criteria, placeholders, and missing measurable outcomes to ensure documentation quality before engineering work begins.

Constitution-aligned enforcement validates generated tasks against .specify/memory/constitution.md to identify critical conflicts. It reports actionable gaps where task definitions or plans deviate from established project principles before implementation starts.

Run spec and task coverage validation after task generation produces a complete tasks.md file. This timing ensures all three core artifacts exist for cross-checking, allowing you to resolve coverage gaps and underspecified items before any coding effort begins.

Spec analysis enforces strict read-only reporting, meaning your existing spec.md, plan.md, and tasks.md files are never modified. The process only outputs a structured findings report identifying documentation QA issues for manual resolution.

Coverage gaps occur when generated tasks fail to fully implement requirements defined in spec.md. Cross-artifact consistency checking identifies these missing task-to-spec mappings and reports them as structured findings alongside any terminology drift or underspecified items.