speckit-checklist

Generate a requirements quality checklist by running a skill that evaluates specification completeness, clarity, consistency, acceptance criteria, and traceability. It outputs structured English-language checklist items stored under the checklists directory to validate requirements before coding begins.

Requirement traceability links specifications to their implementation and tests. A checklist verifies traceability by generating items that confirm each requirement has corresponding acceptance criteria, scenario coverage, and unit-test mappings, ensuring no gaps exist in the specification workflow.

Yes, speckit-checklist works with .specify-based feature directories. It loads project context directly from the .specify directory and appends generated quality evaluation results to existing checklists stored under the checklists path in your project.

Validate edge cases and non-functional requirements by generating a structured checklist that enforces quality checks across dimensions like scenario coverage, edge cases, and non-functional requirements. This ensures specifications capture all critical boundary conditions and performance constraints before development.

Yes, you can use a canonical template for checklist items to ensure consistent requirement evaluation. The skill provides a standardized template structure that enforces uniform quality checks across completeness, clarity, consistency, and acceptance criteria dimensions for auditability.

Requirements often have gaps and ambiguity due to missing edge cases, unclear acceptance criteria, or incomplete scenario coverage. Generating a structured quality checklist identifies these issues early by enforcing evaluation across dimensions like clarity, consistency, and non-functional requirements.