speckit-checklist

To generate a requirements-quality checklist, provide your feature specifications and the system will produce structured items evaluating completeness, clarity, consistency, measurability, and coverage for your project.

Detect gaps and ambiguities in spec.md and plan.md files by applying a tailored checklist that cross-references your feature docs to surface missing scenarios and untestable natural language statements.

A requirements-quality checklist is a structured set of validations, like unit tests for requirements, used when you need to ensure your written specifications are complete, unambiguous, and testable before development.

Yes, you can use your existing tasks.md file alongside spec.md and plan.md to check for missing scenarios, as the checklist generation integrates with these artifacts to detect coverage gaps.

The best way to ensure feature requirements are measurable and consistent is to apply a validation checklist that evaluates each statement against criteria for clarity, measurability, and alignment with project spec sections.

You do not need complete feature docs; the checklist generation applies progressive disclosure and branching questions to tailor the output based on available spec artifacts, even when some are missing.