speckit-checklist

You can validate feature requirements by generating a structured quality checklist that assesses completeness, clarity, consistency, and measurability. This checklist identifies ambiguities, missing scenario coverage, and weak acceptance criteria before development starts.

A requirements quality checklist is a set of validation items that test written specifications for issues like inconsistency and weak acceptance criteria. In PR review workflows, it identifies requirement gaps and traceability issues early, ensuring implementation matches intended feature behavior.

Generate a checklist that evaluates scenario coverage and edge cases against your specification sections. The output requires checklist items to reference spec sections or explicitly mark gaps, ensuring boundary conditions and non-functional requirements are addressed.

Yes, speckit-checklist generates the requirements quality checklist from your current feature's spec-kit project context. It relies on this existing specification data to produce traceability-focused checklist items that reference specific spec sections or flag missing requirements.

The best way to identify missing non-functional requirements is to run a checklist generation command that analyzes your spec-kit context. It produces structured checklist items across completeness and traceability dimensions, explicitly marking conflicts, assumptions, and coverage gaps.

Standard quality assurance often checks implementation behavior rather than the requirements themselves. A requirements-quality checklist specifically targets specification ambiguities, inconsistencies, and missing scenario coverage, requiring explicit references to spec sections to expose hidden gaps.