requirement-quality-checklist

# requirement-quality-checklist — "Unit Tests for English" > **Activation**: manual-only via `/spawn requirement-quality-checklist <PLAN-NNN>`. > Validates REQUIREMENTS WRITING QUALITY, not implementation. ## Purpose Port of github/spec-kit's `/speckit.checklist` (`templates/commands/checklist.md:L253-L266`). Implements "Unit Tests for English" doctrine: checklists validate the QUALITY OF THE WRITING in the requirements, not the behavior of the system. ## Prohibited patterns (reject at output time) The following item-starts are REJECTED — they belong in test suites, not in a requirements-quality checklist: - `Verify ...` — implementation testing language. - `Test ...` — implementation testing language. - `Confirm ...` — implementation testing language. - `Validate that <code does X>` — implementation testing language. ## Categories (per `checklist.md:L30-34`) 1. **Completeness** — is the requirement fully specified? 2. **Clarity** — is the language unambiguous? 3. **Consistency** — does it agree with other requirements? 4. **Coverage** — does the spec cover all stated functionality? 5. **Edge Cases** — are boundary + failure conditions stated? ## Output format Writes structured checklist artifact to: ``` .claude/plans/PLAN-NNN/checklist.md ``` Each item: - Falsifiable (a human can render a yes/no verdict by reading the spec). - Cites a specific line anchor in PLAN-NNN body (`L<NNN>` or `§<section>`). - Belongs to one of the 5 categories. Limit: **50 items max**....