speckit-checklist

To generate a requirements checklist, provide your feature context including spec, plan, and tasks. The tool analyzes this context to produce domain-specific checklists evaluating completeness, clarity, consistency, and measurability for QA validation.

A unit-test-for-requirements checklist evaluates feature requirement quality by validating completeness, clarity, consistency, measurability, coverage, and traceability. It analyzes feature specs and plans to produce domain-specific items that act as rigorous tests for requirements.

To ensure traceability across requirements, the checklist generator analyzes your current feature context from spec, plan, and tasks. It produces structured checklist items that map validation criteria directly to your documented feature requirements.

Yes, you can append new checklist items to existing domain files. The tool creates or updates checklists under the checklists folder using domain-based filenames, preserving existing content by appending new validation items.

The best way to validate non-functional requirements and edge cases is using a structured QA checklist. It analyzes your spec and plan to generate domain-specific items that explicitly evaluate coverage, edge cases, and non-functional constraints.

You need to provide the current feature context, specifically your spec, plan, and tasks. The tool uses this input data to produce domain-specific checklists that validate quality dimensions and formats results for the checklists repository.