speckit-checklist

You generate a requirements checklist by loading spec-kit feature context from spec.md, plan.md, and tasks.md files, then converting them into unit-test style items that validate completeness, clarity, consistency, and measurability.

A requirements-quality checklist identifies missing details, unclear wording, inconsistencies, and weak acceptance criteria in feature specifications before implementation starts, ensuring scenario coverage and traceability.

You ensure coverage by generating checklist items that validate primary flows alongside alternate, exception, recovery, and non-functional scenarios, prompting revisions where requirements gaps or ambiguities exist.

Yes, you can use spec-kit checklists with extension hooks defined in .specify/extensions.yml, optionally incorporating them into checklist generation while skipping invalid hook conditions when needed.

You maintain traceability by generating checklist entries that reference specific spec sections or clearly mark gaps, ambiguities, and conflicts to drive revisions, using a stable CHK### ID scheme in the output markdown.

No, generating a requirements checklist preserves existing content by appending new checklist markdown into the FEATURE_DIR/checklists directory, ensuring your previous specification artifacts remain intact.