speckit-checklist

To generate a requirements quality checklist from a spec.md file, use a tool that parses your feature folder and groups validation items by completeness, clarity, consistency, and measurability. It creates or appends domain-named markdown files under the feature directory's checklists folder.

Requirement traceability in feature specs links requirements to their implementation and tests. It is validated by generating a checklist that enforces traceability markers, ensuring every written feature requirement has corresponding acceptance criteria and coverage before implementation begins.

To validate the completeness and clarity of written feature requirements for PR review, generate a domain-specific checklist that highlights missing acceptance criteria, non-functional targets, and traceability gaps. This surfaces ambiguities and high-risk gaps so reviewers can assess spec quality.

Yes, you can append new checklist items to an existing markdown file without losing previous content. The checklist generation process preserves existing checklist content, continues the CHK ID sequencing, and safely appends new validation items to the domain-named file.

Yes, you need a .specify directory containing feature folders with spec.md, plan.md, or tasks.md files to create unit-test style checklists. The generation process parses a prerequisites JSON produced by the check-prerequisites script within this directory structure.

The limitation of automated requirement quality scaffolding is that it relies entirely on the presence of a .specify directory and valid prerequisites JSON. It cannot validate requirements outside this structure and focuses solely on generating checklists for gaps, edge cases, and traceability without executing tests.