speckit-analyze

To find inconsistencies across spec.md, plan.md, and tasks.md, analyze the artifacts for duplications, ambiguities, and underspecified items before code changes. This cross-artifact analysis identifies misalignments early and returns a structured report with an optional remediation plan.

Cross-artifact quality analysis should run after task generation produces a complete tasks.md and before any code changes. This timing ensures you validate alignment and identify underspecified items early, preventing implementation drift in your speckit project structure.

Constitution validation works by checking your spec.md, plan.md, and tasks.md against the .specify/memory/constitution.md file. This read-only analysis enforces project rules while generating a structured report of any constitutional misalignments found across artifacts.

Yes, analyzing your artifacts can automatically generate an optional remediation plan for underspecified items, duplications, and ambiguities. The analysis returns this plan alongside a structured report to guide quick risk mitigation before implementation begins.

The limitation of read-only analysis is that it cannot directly modify your spec.md, plan.md, or tasks.md files. It strictly identifies inconsistencies and validates the constitution, returning a structured report and remediation plan for you to apply manually.

Yes, speckit-analyze works specifically after the speckit.tasks command has produced a complete tasks.md file. It evaluates the generated tasks against your spec.md and plan.md to find cross-artifact inconsistencies before you start coding.