speckit-analyze

Cross-artifact consistency analysis identifies inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md. It produces a structured report after task generation, highlighting conflicts and underspecified items before implementation begins.

Yes, cross-artifact consistency analysis enforces strict read-only analysis of spec.md, plan.md, and tasks.md. It generates a structured report without editing source files, and any proposed remediation plan requires explicit user approval before execution.

Run cross-artifact consistency analysis after the speckit.tasks phase completes and produces a complete tasks.md within a .specify project structure. This timing ensures all three artifacts exist and are ready for quality and consistency validation.

Artifact quality analysis references the project constitution during validation to highlight conflicts that violate MUST principles. It surfaces these constitutional violations within the structured analysis report, ensuring foundational project rules are respected.

The best way to resolve ambiguities is through the optional remediation plan proposed after consistency analysis. This plan requires explicit user approval before any edits are made, ensuring controlled and reviewed fixes for underspecified items and duplications.

No, cross-artifact analysis operates after speckit.tasks has produced a complete tasks.md within the .specify project structure. A fully generated tasks.md is required to accurately identify inconsistencies and ambiguities across all three artifacts.