speckit-checklist

To generate a requirements checklist for spec review, provide a short focus area like UX accessibility to the checklist generator. It extracts signals from your spec.md and plan.md files to produce traceable, measurable requirement statements grouped by quality dimensions.

Traceability in requirement tests links checklist items directly to specific spec sections like Spec §X.Y. This mechanism ensures high review readiness by mapping measurable statements back to original feature specification details.

You check scenario coverage for edge cases by generating a domain-scoped checklist that flags gaps using markers like [Gap] or [Ambiguity]. It evaluates primary, alternate, exception, and non-functional scenario classes within your feature specifications.

Yes, you can append new items to an existing spec checklist file. The tool saves outputs to FEATURE_DIR/checklists/ and supports incremental checklist building by continuing the CHK numbering sequence for newly extracted requirement statements.

Yes, speckit-checklist works for UX accessibility requirements by accepting a targeted focus area in your prompt. It generates a tailored requirements-quality checklist that validates clarity, completeness, and measurability for interactive components.

The limitation of using unit tests for requirements writing is that they focus strictly on requirement quality dimensions like clarity and consistency, rather than verifying actual software implementation or functional code execution.