speckit-checklist

To generate a requirements checklist from a feature specification, run the speckit-checklist tool on your project. It analyzes spec.md, plan.md, and tasks.md files to produce traceable, test-oriented prompts categorized by quality dimensions.

Spec traceability links generated checklist items directly to specific sections within your feature specification. By mapping CHK IDs to spec.md, plan.md, and tasks.md content, it ensures every requirement validation prompt is anchored to its source documentation.

Feature requirements are evaluated across seven quality dimensions: Completeness, Clarity, Consistency, Measurability, Coverage, Edge Case Coverage, and Non-Functional aspects. This ensures language-focused checks rather than implementation details.

Yes, you can append new checklist items to existing feature documentation. The tool creates or augments checklists under the FEATURE_DIR/checklists/ directory with unique CHK IDs while preserving any existing content already present.

Yes, a .specify directory structure is required. The checklist generation operates on projects using this spec kit structure and relies on feature docs like spec.md, plan.md, and tasks.md to extract context and produce traceable QA prompts.

A specification checklist focuses on requirement quality and traceability rather than implementation details. It converts vague specs into concrete, categorized QA prompts, ensuring completeness, clarity, and edge case coverage before coding begins.