speckit-analyze

To check spec.md, plan.md, and tasks.md for inconsistencies, run a cross-artifact consistency analysis after task generation. It identifies duplication, ambiguity, underspecification, and ordering conflicts across the files without modifying them.

Requirements coverage mapping flags requirements with zero tasks and tasks that do not map to requirements or stories. It cross-references spec.md and tasks.md to ensure every specified requirement has corresponding implementation tasks.

Yes, you can validate constitution compliance by checking spec.md, plan.md, and tasks.md against .specify/memory/constitution.md. The constitution file serves as the non-negotiable authority for alignment validation.

No, the spec analysis is non-destructive. It performs read-only cross-artifact checks and produces a token-efficient Markdown report of findings and next actions without modifying spec.md, plan.md, or tasks.md.

Run cross-artifact consistency checks after tasks.md generation succeeds and before starting implementation. This timing catches coverage gaps, terminology drift, and ambiguity early, ensuring spec, plan, and tasks align before coding.

Cross-artifact analysis detects duplication, ambiguity, underspecification, terminology drift, ordering conflicts, and constitution compliance issues. It also flags requirements with zero tasks and tasks lacking mappings to requirements or stories.