What problem does it solve? Specification-driven projects often drift out of sync: requirements in spec.md lack matching tasks, plan.md references entities the spec never defines, and ambiguous wording slips through until implementation. This Skill performs a read-only, cross-artifact consistency analysis across spec.md, plan.md, and tasks.md so teams catch inconsistencies, duplications, ambiguities, and coverage gaps before writing code. ## Core Features & Use Cases - Cross-Artifact Detection Passes: Detects duplications, ambiguities, underspecification, constitution violations, coverage gaps, and inconsistencies across the three core spec-kit artifacts. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW severity findings, a requirement-to-task coverage table, and metrics such as coverage percentage and ambiguity counts. - Constitution Enforcement: Validates artifacts against the non-negotiable project constitution in .specify/memory/constitution.md, flagging any MUST-principle conflict as CRITICAL. - Use Case: After running /speckit-tasks on a new feature, run this analysis to discover that a performance success criterion has no implementing task and that two requirements duplicate each other, then remediate before /speckit-implement. ## Quick Start Ask the assistant to run the speckit-analyze skill to check the current feature's spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps.
