speckit-checklist

To generate a requirements quality checklist, provide a focus area like "ux accessibility" and the tool reads spec.md, plan.md, and tasks.md from your .specify FEATURE_DIR to produce domain-focused validation items grouped by quality dimension.

You validate written feature requirements by generating a checklist that surfaces gaps, ambiguities, and missing acceptance criteria, allowing authors and reviewers to assess spec quality before implementation begins.

Yes, checklist generation works directly with spec-kit project structures. It requires access to a .specify repository, reads the FEATURE_DIR on demand, and creates or appends files in the checklists subdirectory.

You can append new checklist items safely. The tool preserves existing content and traceability references, generates sequential CHK IDs, and appends domain filenames within FEATURE_DIR/checklists/ without overwriting previous validation items.

The best way to narrow checklist scope is providing a specific domain. The tool generates up to three targeted clarification questions derived from user input and spec signals to narrow scope and depth before producing the checklist.

Generated requirement checklists are grouped by quality dimension to systematically validate completeness and traceability. This structure helps reviewers assess specific requirement quality areas rather than evaluating items in isolation.