speckit.checklist

Validate feature requirements by generating structured checklists that assess completeness, clarity, consistency, measurability, coverage, and traceability. This catches specification defects early by producing categorized, testable quality checks for spec refinement.

Create a PR review checklist by running a checklist generation flow against your feature directory. The process reads spec.md, plan.md, and tasks.md contexts to produce categorized items with CHK### identifiers that highlight missing acceptance criteria and ambiguous terms.

Requirements traceability during spec review tracks validation items by emitting CHK### identifiers and referencing specific spec sections. This mechanism supports review and tracking by linking each generated checklist item directly to the written feature specification.

Automated checklists find missing acceptance criteria and unaddressed edge cases by evaluating requirement quality rather than implementation behavior. They act as unit tests for English, producing measurable items that expose ambiguity and gaps in coverage.

Checklist validation works with plan.md and tasks.md files by reading them alongside spec.md to derive focused checks. This context-aware approach ensures the generated items accurately support QA gating and release readiness assessments.

Automated checklists for spec refinement focus strictly on evaluating written requirement quality and completeness, meaning they do not test actual implementation behavior. They serve as a quality gate to catch specification defects before development begins.