review-fulllisted

# Full Review - Pre-Release Check Mile wide, inch deep. Cross-domain release readiness, not a deep specialist review. **Use this when:** Pre-release gate, major milestone check, or when multiple domains changed significantly and you need a single go/no-go assessment. **Don't use this when:** You need deep review of one area - use /review-code, /review-commands, /review-plan, /review-ux, or /review-browser instead. This command will recommend which specialist review to run if it finds areas needing deeper attention. ## 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 4. **Don't duplicate specialist reviews** - Prioritize cross-domain issues, release blockers, and interactions between code, UX, scope, and operations. If something needs deeper investigation, recommend which specialist command to run next. </rules> ## How to Review <procedure> Read the changed files and any relevant plan file. Auto-detect the most recently modified `PLAN-*.md` in `plans/` (also check the project root for legacy plan files). If no plan file exists, skip plan comparison and note it in the summary. 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 to evaluate against. Then pick one of two modes: **Small change** (1-2 files, minor update): Review in a