speckit-analyze

To check spec.md, plan.md, and tasks.md for inconsistencies before coding, perform a read-only consistency review. This cross-artifact analysis detects duplication, conflicts, and requirement gaps across specification, planning, and task documents without modifying files.

Requirement coverage mapping in software planning is the process of validating that every feature requirement is accurately tracked across architecture plans and task breakdowns. It ensures implementation readiness by identifying missing requirements and untracked work before development.

Validating implementation readiness for a spec-kit workflow involves inspecting specification artifacts to ensure constitution alignment and complete task mapping. This structured reporting identifies ambiguities and contradictory architecture decisions before software implementation begins.

Yes, a read-only consistency check can find missing requirements in task lists by comparing feature requirements against task breakdowns. It maps requirement coverage and reports alignment findings without modifying the underlying documents.

speckit-analyze does not modify specification and planning files during review. It requires strictly read-only document inspection to perform quality validation and report duplication, ambiguity, and alignment findings safely.