speckit-analyze

To check for inconsistencies across spec, plan, and task documents, analyze the artifacts to identify cross-artifact misalignments, gaps, and duplications before implementation begins.

Cross-artifact gap analysis in software planning compares specifications, plans, and tasks to highlight missing mappings and traceability gaps, ensuring all requirements are fully covered and traceable.

You should analyze tasks for consistency with your project specification immediately after task generation, detecting ambiguities and duplications early to prevent rework before implementation.

To ensure traceability from requirements to tasks before coding, perform a cross-artifact analysis that detects missing mappings and enforces constitution-compliant checks across all planning documents.

Yes, you can detect duplicate entries across spec.md, plan.md, and tasks.md by running a cross-artifact analysis that highlights duplications and suggests concrete remediation improvements for alignment.

Automated spec and plan consistency checks require distinct spec.md, plan.md, and tasks.md artifacts to function, meaning incomplete or unstructured planning documents will limit gap detection and traceability enforcement capabilities.