This generates quality assurance checklists for your requirements documents, not your code. Think of it as unit tests for your specs. Instead of checking if buttons work, it asks whether your requirements define what "prominent display" actually means, whether error handling scenarios are documented, or if accessibility requirements exist at all. It reads your spec.md, plan.md, and tasks.md files, then produces numbered checklist items that systematically probe for completeness, clarity, consistency, and gaps. Useful during PR reviews or before handoff when you want to catch ambiguous requirements before they become implementation surprises. Creates separate checklist files for different domains like ux.md or security.md.
npx skills add https://github.com/forztf/open-skilled-sdd --skill speckit-checklist-zh