speckit-analyze

To check for inconsistencies across spec, plan, and tasks files, run a cross-artifact analysis to map functional requirements, constraints, and tasks. This detects gaps, conflicts, and underspecified items before coding begins.

Cross-artifact analysis identifies duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. It produces a structured report with a coverage matrix, high-priority issues, and recommended next actions.

You should run a consistency check only after a complete tasks.md has been generated from your spec and plan. Running it earlier will not produce a valid coverage matrix or detect cross-artifact conflicts.

No, cross-artifact analysis requires a fully generated tasks.md file to function. The analysis logic depends on mapping tasks against functional requirements and constraints to detect coverage gaps.

The best way to identify underspecified items is to generate a structured coverage matrix mapping requirements to tasks. This highlights missing elements and risk signals across the spec and plan artifacts.

To minimize context load during analysis, use a progressive-disclosure model that outputs a compact structured report. This limits data processing to high-priority issues and recommended next actions only.