speckit-checklist

Generate a requirements quality checklist by reading feature context from a spec-kit workspace and producing a structured file under checklists/ that evaluates completeness, clarity, consistency, and coverage. It assigns incremental CHK identifiers and maintains traceability to source spec sections.

Unit-test style verification for requirements tests written specification quality—completeness, clarity, consistency, and coverage—rather than testing software implementation code. It enforces a structured template to evaluate spec documents systematically.

Yes, the requirements checklist tool requires a spec-kit workflow with a .specify/ directory. It reads related spec documents from this workspace to generate domain-focused checklists tailored to your feature.

Maintain traceability by assigning incremental CHK identifiers to each checklist item and linking them directly to corresponding source spec sections. The tool creates or appends to checklists/speckit-checklist.md automatically.

Yes, you can append new quality checks to an existing checklist file. The tool creates or appends to checklists/speckit-checklist.md, assigning incremental CHK identifiers to maintain continuity across your requirements verification items.

Checklist-based requirements verification focuses solely on evaluating written specification quality—completeness, clarity, consistency, coverage—and does not test actual software implementation. It requires a spec-kit workspace with a .specify/ directory to function.