speckit-checklist

To generate a requirement checklist for spec-kit feature files, run the skill with your arguments. It loads spec.md, plan.md, and tasks.md to produce an append-only checklist evaluating completeness, clarity, consistency, and traceability criteria.

A feature specification checklist should cover completeness, clarity, consistency, measurability, coverage, edge cases, and traceability. These criteria ensure product features are rigorously validated before development to reduce ambiguity and rework.

Yes, you can use requirement traceability checklists for QA and reviewer guidance. The generated checklist explicitly guides authors, reviewers, and QA teams through structured quality checks tailored to the specific feature context.

To validate edge cases before development, the skill reads feature context from spec.md, plan.md, and tasks.md. It then converts your inputs into structured checklists that enforce edge case coverage, reducing ambiguity and rework.

Yes, checklist generation works without external dependencies. The skill operates independently to parse user inputs and feature context files, outputting a maintainable checklist file in a dedicated checklists folder.

The best way to maintain requirement checklists across multiple feature domains is using an append-only checklist file structure. The skill produces one maintainable file per feature or domain in a dedicated checklists folder.