speckit-checklist

To generate a requirements quality checklist, load your feature specifications from spec, plan, or tasks contexts. The system validates completeness, clarity, and testability, outputting a Markdown file under specs/<feature>/checklists/<domain>.md with unique CHK IDs and traceable spec section references.

Requirements traceability links validation items directly to source documents. This checklist applies traceability by appending references like [Spec §X.Y] to each generated check, ensuring every validation criterion aligns with a specific section of your original feature specification.

You validate edge cases and acceptance criteria by evaluating the feature specification against quality dimensions like completeness, coverage, and measurability. The generated checklist systematically identifies gaps in these areas to ensure all scenarios are addressed prior to development.

Yes, checklist generation supports domain-specific feature requirements. It creates a targeted Markdown file under specs/<feature>/checklists/<domain>.md, allowing authors and reviewers to validate requirements quality within a specific domain context before implementation begins.

You preserve a history of requirement quality checks by generating a new checklist file for each validation run. Every execution creates a distinct Markdown document with unique CHK IDs under the specs/<feature>/checklists directory, maintaining an auditable trail of requirement reviews.