speckit-checklist

You validate feature specification quality by generating a requirements checklist that assesses clarity, completeness, consistency, and measurable acceptance criteria across defined scenarios. This ensures specs are implementation-ready by identifying gaps and ambiguities early.

To ensure scenario coverage and traceability in feature requirements, generate a checklist categorizing checks for primary, alternate, exception, and non-functional scenarios. This checklist references spec sections to highlight gaps, conflicts, and assumptions for review.

You generate acceptance criteria checklists by running a checklist generation process on spec-kit feature folders containing spec.md. The process appends a traceability-focused checklist under the feature directory's checklists folder for review.

Requirements unit testing verifies specification quality rather than software behavior. It checks whether written requirements are complete, unambiguous, consistent, and measurable, categorizing checks to validate the spec itself before any implementation occurs.

Yes, you can use a requirements checklist to find ambiguities and conflicts in your feature spec. The generated checklist categorizes checks specifically for ambiguities, conflicts, and dependencies, providing spec-section references to improve the spec during review.