speckit-analyze

To check spec.md, plan.md, and tasks.md for inconsistencies, you can cross-reference the artifacts to identify duplications, ambiguities, and underspecified items before implementation. This surfaces misalignments early through a structured analysis report.

Cross-checking speck-kit artifacts without modifying files requires a strictly read-only analysis process. It evaluates the documents against constitution.md principles and outputs a structured report with an optional remediation plan that requires explicit approval.

Constitution.md enforces consistency by providing the foundational principles the analysis relies on to surface findings. The read-only evaluation compares spec.md, plan.md, and tasks.md against these rules to flag actionable remediation guidance.

You should run a cross-artifact consistency analysis immediately after tasks.md is produced. This timing ensures early detection of misalignments across spec.md, plan.md, and tasks.md before you begin the implementation phase.

You cannot automatically fix ambiguities found across spec, plan, and tasks files because the analysis is strictly read-only. It generates a remediation plan, but explicit user approval is required before any edits would be performed.

Spec-kit consistency analysis requires no external dependencies or components. It operates strictly as a read-only process relying on the existing .specify/memory/constitution.md file to generate its structured analysis report.