What problem does it solve? Before implementation begins, specification artifacts often contain contradictions, ambiguous requirements, and coverage gaps that cause rework. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md so teams catch these issues early. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects duplications, ambiguities, underspecified requirements, terminology drift, and conflicting requirements across the three core spec-kit artifacts. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, reporting requirements with zero task coverage and unmapped tasks. - Constitution Enforcement: Validates artifacts against the project constitution (.specify/memory/constitution.md), treating MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit-tasks, a team lead runs this analysis and receives a severity-ranked report showing that a performance requirement has no implementing task and that two requirements conflict on framework choice, before any code is written. ## Quick Start Run /speckit-analyze after task generation to produce a read-only consistency and coverage report for the current feature's spec, plan, and tasks.