speckit-analyze

Mapping requirements to tasks involves tracing each specification entry to its corresponding task entry to identify unmapped requirements or tasks lacking traceability. This semantic requirement-to-task mapping highlights coverage gaps before implementation handoff.

The best way to detect coverage gaps is to perform semantic requirement-to-task mapping across your spec.md and tasks.md files. This highlights unmapped requirements or orphaned tasks lacking traceability before implementation begins.

No, cross-artifact consistency analysis is a non-destructive, read-only process. It evaluates your spec, plan, and tasks files and produces a compact Markdown analysis report without modifying your original repository files.

To flag constitution conflicts in a spec-kit feature directory, the analysis validates artifacts against project constitution principles, marking violations as CRITICAL. It also assigns severity classifications to other findings like ambiguities and duplications.

You need to run a consistency and quality analysis on specification artifacts when preparing for implementation handoff. It serves as a validation gate to catch terminology drift, underspecification, and coverage gaps across your spec, plan, and tasks files.