speckit-checklist

To generate a requirement quality checklist, the Skill reads spec-kit project context from the .specify/ directory and creates structured checks for completeness, clarity, consistency, coverage, and traceability. It outputs these items into the checklists/ directory.

Requirement traceability links features to their origin and implementation. A generated checklist ensures traceability by creating unit-test style checks that validate whether each requirement in spec.md, plan.md, and tasks.md is consistently mapped and covered.

Yes, you can append new validation items to an existing requirements checklist. When a checklist already exists under the checklists/ directory, the Skill adds new domain-specific checks for completeness and clarity without overwriting previous entries.

The Skill is designed for spec-kit style workflows and uses the optional .specify/ directory to load feature context. It can still generate quality checklists, but providing spec.md, plan.md, and tasks.md context ensures maximum coverage and consistency.

The best way to check completeness and consistency is to generate a unit-test style checklist from your specification. This process analyzes your feature context and produces structured validation items addressing ambiguity, coverage gaps, and traceability.

You should not rely solely on an automated checklist when your project lacks a defined specification structure. Without the foundational context provided by spec.md, plan.md, and tasks.md files, the generated checks cannot accurately validate requirement traceability or coverage.