speckit-checklist

To generate a requirements checklist for feature specs, run the speckit-checklist workflow from your repository root to produce Markdown items evaluating quality dimensions under the checklists directory.

A spec-kit checklist is a unit-test style validation list for requirement completeness, clarity, consistency, and coverage. You need it to ensure your feature specifications are clear and testable.

Yes, you can append new checklist items to an existing requirements file. The workflow maintains sequential incremental numbering like CHK001 and CHK002, appending Markdown items to existing checklist files when present.

Yes, the checklist workflow requires a .specify directory. It is applied to spec-kit projects containing this directory structure and supports extension hooks configured via .specify/extensions.yml for pre- and post-checklist tasks.

The best way to maintain traceability in feature specification checklists is to generate Markdown items that include direct references to spec sections. This preserves alignment with your project requirements during validation.

Automated checklist generation for specifications is limited to spec-kit projects with a .specify directory and standard template workflows. It focuses on language-focused quality dimensions rather than functional testing or code validation.