What problem does it solve?
It helps you validate that your requirements are complete, clear, consistent, and testable before implementation begins, reducing ambiguity and rework.
Core Features & Use Cases
- Requirement Unit Testing: Produces checklist items that assess requirement quality (completeness, clarity, consistency, measurability, coverage) rather than checking whether code works.
- Scenario Coverage: Encourages inclusion of primary, alternate, exception/error, recovery, and non-functional requirements, including edge cases and rollback expectations when state changes.
- Append-Only Checklist Growth: Creates a domain checklist file (e.g., ux.md/api.md) or appends new items while preserving existing content and CHK numbering.
- Traceability-First Items: Forces most checklist items to reference spec sections (e.g., [Spec §X.Y]) or explicitly mark gaps, ambiguities, conflicts, assumptions, and missing criteria.
- Use Case Example: Use it during PR review to improve a feature spec by identifying missing acceptance criteria, undefined terms, inconsistent requirements, and unaddressed failure paths.
Quick Start
Run the speckit-checklist skill with your feature domain or focus area as the argument to generate an appended checklist for requirements quality validation.