speckit-checklist

To validate feature specification quality, generate requirement-focused checklists that assess completeness, clarity, consistency, measurability, and coverage of written specs to ensure they are implementation-ready. This approach tests the specification language rather than the implementation itself.

Generate requirement checklists from spec.md and plan.md files by reading them alongside tasks.md in a Spec Kit repository, then produce or append domain checklist files inside the FEATURE_DIR/checklists/ directory with sequential CHK### identifiers.

The best way to group requirement validation checks is by quality dimensions such as Completeness, Clarity, Consistency, Coverage, Edge Cases, and NFRs, ensuring each item includes traceability references or [Gap] markers to track specification gaps accurately.

Yes, requirement checklist generation works with Spec Kit repositories that contain a .specify directory, reading the existing spec.md, plan.md, and tasks.md files to derive context-aware checklist items for your feature specifications.

Implementation-testing phrases are prohibited in requirement checklists because the goal is to validate the written feature specification's quality and measurability, not to test the implementation, ensuring the spec itself is clear and complete.

Yes, you can append new checklist items to existing domain-named files in FEATURE_DIR/checklists/ while preserving existing CHK### identifiers, and the generation process enforces sequential numbering for any newly added requirement validation checks.