Audit requirement quality across change artefacts. This is a requirements linter, not a test runner: if the spec is code written in English, the checklist is its unit test suite.

Input: Optionally specify a change name and the checklist's focus (e.g., "security", "ux for the checkout"). If the change is omitted, infer from context or ask.

Ownership: the checklists this skill writes belong to the reviewer. A tick means the reviewer judged that requirement-quality criterion satisfied; it never means implementation work is done. This skill writes items unticked and never ticks them; it may help evaluate them only when the reviewer asks. checklists/requirements.md is the spec-quality checklist kept by spec-kit-specify and spec-kit-clarify, not one of these.

Steps

Load artefacts

Load what exists under specs/changes/<name>/:
- spec.md, plan.md, tasks.md
Also load FRAMEWORK.md for governing principles alignment. Load only the parts relevant to the checklist's focus; summarise long sections rather than copying them.

spec-kit-checklist