speckit-analyze

Cross-artifact consistency checks validate alignment across spec.md, plan.md, and tasks.md by identifying inconsistencies, duplications, ambiguities, and underspecified items. The analysis generates remediation-ready reports to improve cross-artifact quality before implementation.

Detecting ambiguities and placeholders in spec-kit artifacts involves scanning spec.md, plan.md, and tasks.md for unresolved markers like TODOs, TKTK, or ???. This analysis highlights underspecified items to ensure full requirement coverage before development begins.

You need cross-artifact traceability mapping immediately after task generation produces tasks.md. Running the analysis at this stage verifies that spec.md, plan.md, and tasks.md are fully aligned and helps identify coverage gaps before assigning implementation tasks.

No, this analysis requires a Speckit-style project where spec.md, plan.md, and tasks.md all exist. It is designed specifically for cross-artifact verification and cannot perform consistency checks if task generation has not yet produced tasks.md.

Generated tasks misalign with project plans and specifications due to duplications, ambiguities, or underspecified items introduced during task generation. Running a cross-artifact consistency analysis identifies these gaps and provides remediation-ready insights to realign the documents.

No, the consistency analysis does not automatically fix gaps. It produces a structured report with remediation-ready insights and coverage mapping, guiding you on how to resolve inconsistencies and ambiguities across spec.md, plan.md, and tasks.md manually.