checklist
Generates a checklist for the feature. The checks test the quality of the requirements, not the code.
- Kind
- Prompt
- Works with
- Claude Code, Codex, GitHub Copilot, Cursor, Windsurf / Devin, Cline
- Source
- github/spec-kit @ c00dc0551583
- Path
- templates/commands/checklist.md
- License
- MIT
- Jobs
- Review
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
## Checklist Purpose: "Unit Tests for English" **CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain. **NOT for verification/testing**: - ❌ NOT "Verify the button clicks correctly" - ❌ NOT "Test error handling works" - ❌ NOT "Confirm the API returns 200" - ❌ NOT checking if code/implementation matches the spec **FOR requirements quality validation**: - ✅ "Are visual hierarchy requirements defined for all card types?" (completeness) - ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity) - ✅ "Are hover state requirements consistent across all interactive elements?" (consistency) - ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage) - ✅ "Does the spec define what happens when logo image fails to load?" (edge cases) **Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works. **Ownership and checkbox lifecycle**: …