What problem does it solve? Before implementation begins, inconsistencies between a feature's specification, technical plan, and task list can cause rework and missed requirements. This Skill performs a read-only, cross-artifact analysis to surface duplications, ambiguities, underspecified items, and coverage gaps before any code is written. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects terminology drift, conflicting requirements, and data entities referenced in one artifact but missing from others. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero task coverage and tasks with no mapped requirement. - Constitution Validation: Treats violations of project constitution MUST principles as CRITICAL findings that must be resolved before implementation. - Severity-Ranked Report: Produces a structured Markdown report with findings categorized by severity (CRITICAL, HIGH, MEDIUM, LOW), coverage metrics, and suggested next actions. - Use Case: After running /speckit-tasks to generate tasks.md, run this analysis to confirm every requirement has task coverage and no constitution conflicts exist before starting /speckit-implement. ## Quick Start Ask the assistant to run the speckit-analyze skill to check consistency across spec.md, plan.md, and tasks.md in the current spec-kit project.
