speckit-analyze

Run cross-artifact consistency analysis on spec.md, plan.md, and tasks.md after task generation to detect mismatches, duplications, and ambiguities. It builds semantic models to catch spec-plan-task inconsistencies early before implementation begins.

Requirements traceability analysis validates that tasks.md fully covers requirements and success criteria defined in spec.md and plan.md. It identifies coverage gaps and underspecified items, ensuring complete documentation before development starts.

Apply semantic modeling to specification, planning, and task documents to flag overlapping definitions and unclear requirements. This produces a structured quality report with specific metrics and recommended next actions for resolution.

Yes, consistency analysis targets Speckit projects using the spec-kit project structure with FEATURE_DIR-derived artifacts and the required constitution file. It performs read-only reporting to ensure non-destructive validation of existing documentation.

Run documentation validation immediately after generating tasks.md to verify that tasks fully cover requirements and success criteria in spec.md and plan.md. This confirms spec-plan-task alignment before implementation begins.

Read-only consistency analysis is limited to non-destructive reporting without modifying artifacts. It cannot auto-fix detected issues, but recommends whether to halt for CRITICAL issues or proceed with improvements for lower-severity problems.