speckit-checklist

You create unit tests for requirements quality by running a checklist command against your specification directory, which validates completeness, clarity, and coverage in English before implementation begins.

A requirements quality checklist validates completeness, clarity, consistency, coverage, and edge cases by specifying measurable acceptance criteria and traceability references to spec sections.

Yes, you can use it with .specify-based project structures. It loads spec context from your plan, tasks, and artifacts to guide reviewers and generate domain-based checklists.

To generate a quality checklist, run the checklist command against your SPEC directory. It produces and stores checklists under a checklists folder with domain-based filenames and sequential CHK IDs.

The best way to ensure traceability is using a consistent CHK numbering scheme with sequential IDs. The generated checklists include traceability references directly mapped to spec sections.

You should avoid automated checklists when specifications lack structured plan, tasks, and artifacts, as the tool relies on .specify-based project context to validate completeness and generate traceability references.