review-commandslisted

# Slash Command Review Be thorough but concise. **Use this when:** Reviewing slash command prompts (.claude/commands/*.md) - prompt quality, workflow completeness, cross-command consistency. **Don't use this when:** Reviewing application code (/review-code), testing a running web app (/review-browser), checking plan completion (/review-plan), 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> Read the command files being reviewed. Then pick one of two modes: **Small change** (1-2 files, minor wording tweaks): Review in a single pass. No sub-agents needed. **Bigger change** (3+ files or new/rewritten commands): Run four focused sub-agents in parallel using the Agent tool, then combine their results: | Sub-agent | What it checks | |-----------|----------------| | **Prompt Engineering** | Clarity of instructions, ambiguities, conflicting directives, missing examples | | **Cross-command Consistency** | Terminology alignment, structure, formatting, prerequisite references across commands | | **Workflow Completeness** | Missing steps, dead ends, assumption gaps, output usability, failure modes | | **Workflow Ergonomics** | Cognitive load, progress visibility, mistake recovery, workflow clarity for