review-planlisted

# Plan Compliance Review Did we build what we said we'd build? Compares implementation against plan/spec. **Use this when:** Checking if implementation matches a plan file in `plans/` - feature completeness, scope drift, quality gates. **Don't use this when:** Reviewing code quality (/review-code), testing a running web app (/review-browser), reviewing command prompts (/review-commands), evaluating end-user UX (/review-ux), or doing a pre-release check (/review-full). ## Critical Rules <rules> 1. **REPORT ONLY** - Do NOT make any changes or edits to files 2. **Wait for approval** - Only fix things after I say "fix it" 3. **Explain simply** - Use plain English, avoid jargon </rules> ## How to Review <procedure> First, find the plan file to review against. Auto-detect the most recently modified `PLAN-*.md` file in `plans/` (also check the project root for legacy plan files). If no plan file exists, pause and ask the user: "I couldn't find a plan file. Which file should I compare against, or would /review-code be more appropriate?" If multiple plan files exist and the most recent one is not clearly complete (all tasks checked off), pause and ask the user: "Which plan file should I evaluate against?" Read the plan file, then read the implementation files. Compare them. Pick one of two modes: **Small change** (1-2 plan tasks, few files): Review in a single pass. No sub-agents needed. **Bigger change** (3+ plan tasks or significant scope): Run four focused sub-agents in