spec-reviewlisted

# Spec Review Skill Review a product or requirements specification before any plan is authored. A spec that ships ambiguous quantifiers, untestable requirements, or undefined non-functional limits forces the plan to guess — and every guess becomes an in-flight pivot. This skill catches those defects while they are still cheap to fix and feeds a tightened spec into plan-author. ## Step 1: Locate the Spec If the user provided a file path as an argument, use that. Otherwise scan for: `**/spec.md`, `**/PRD*.md`, `**/requirements*.md`, `**/*-spec.md`, `**/feature*.md` If multiple candidates exist, use AskUserQuestion to disambiguate. Read the full document — every requirement, not just headers. Specs are dense; one ambiguous clause can corrupt a whole subsystem. ## Step 2: Quick Triage (Optional Fast Path) For a quick signal before committing to a full review, run: ```bash ~/.claude/skills/spec-review/scripts/score-spec.sh <spec-file> ``` This greps for presence of acceptance criteria, non-goals, non-functional requirements, and success metrics. If score < 40%, tell the user the spec needs fundamental work before a full review is worthwhile. ## Step 3: Load Checklists Read ALL of the following checklist files from this skill's directory (`~/.claude/skills/spec-review/`). They contain the full review criteria: - `CHECKLIST-01-CLARITY.md` — Undefined terms, ambiguous quantifiers, hidden actors, contradictions - `CHECKLIST-02-TESTABILITY.md` — Measurable acceptance conditio