speckit-checklist

To generate unit-test-quality checklists from feature requirements, you describe the feature specs and let the system load context from spec.md, plan.md, and tasks.md to produce domain-specific checklist items under checklists/.

Yes, you can append new checklist items to existing files. The system preserves existing checklist entries while adding newly generated domain-specific items to maintain continuity across spec-kit workflows.

Requirement checklists enforce completeness, clarity, consistency, measurability, and coverage dimensions. Each generated item references relevant spec sections to ensure full traceability across the feature documentation.

You validate requirement clarity and completeness before implementation by generating checklists that act as unit tests for requirements, assessing spec.md and plan.md context against enforced quality dimensions.

Yes, the checklist generator works directly within the spec-kit directory structure. It loads feature context from FEATURE_DIR/spec.md, plan.md, and tasks.md to create checklists and integrate with extension hooks.

Automated checklist generation requires existing spec-kit files like spec.md and tasks.md to load context. Without these structured feature requirement files in place, the system cannot generate domain-specific checklists.