What problem does it solve? In spec-driven development, inconsistencies between the specification, implementation plan, and task list often surface only during coding, causing rework. This Skill performs a read-only cross-artifact analysis before implementation begins, catching duplications, ambiguities, coverage gaps, and constitution violations early. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects duplication, ambiguity, underspecification, terminology drift, and conflicting requirements across spec.md, plan.md, and tasks.md. - 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, treating MUST-principle violations as CRITICAL findings. - Use Case: After generating tasks.md with speckit-tasks, run this analysis to receive a severity-ranked findings table, coverage summary, and metrics before starting implementation. ## Quick Start Ask the assistant to run the speckit-analyze skill to check the current feature's spec, plan, and tasks for inconsistencies and coverage gaps.