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. **THE REVIEW PHASE REPORTS ONLY** - Reviewing never edits files; findings are its product. After the report, the same run continues into the auto loop (rule 2), which is what applies fixes 2. **Audit, then auto-fix, with pages** - Plan-compliance findings are audited before the report per M2 in `.claude/skills/shared/hitl-loop.md`, so the report shows survivors only plus an Audited out log for the kills. They do not then wait for a human "fix it": after the report, survivors are auto-fixed and re-verified, and each finding exits as page, digest, or log per `.claude/skills/shared/hitl-loop.md` (pages only per M1 - a gap that traces to actual ship status or a deliberate scope call is M1/M7 territory; saying "report only" keeps a run report-first, M10) 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 projec