competitive-reviewlisted

# Competitive Review Dispatch two competing reviewers before deep analysis. Competition produces more thorough results. ## Purpose Different perspectives catch different issues. Architecture reviewers find structural problems; implementation reviewers find code-level bugs and fact-check claims. Running them in competition ("whoever finds more issues gets promoted") increases thoroughness. ## Triggers Use before ANY complex task involving: - Creating new code - Modifying existing architecture - Making technical decisions - Answering questions about a codebase - Building new features ## Protocol ### Step 1: Announce the Competition Say: **"I'm dispatching two competing reviewers to analyze this."** ### Step 2: Spawn Both Agents IN PARALLEL ```text Task(agent="arch-reviewer", prompt="[full user question + context]") Task(agent="impl-reviewer", prompt="[full user question + context]") ``` Tell each agent: > "You are competing against another agent. Whoever finds more valid issues gets promoted. Be thorough." ### Step 3: Collect Results Wait for both agents to return their analysis. ### Step 4: Merge & Score ```markdown ## Review Competition Results | Reviewer | Issues Found | HIGH | MED | LOW | |----------|--------------|------|-----|-----| | arch-reviewer | X | X | X | X | | impl-reviewer | Y | Y | Y | Y | **Winner: [agent with more HIGH severity issues]** ### Combined Issues (deduplicated) [Merge both lists] ### Verified Facts [From impl-reviewer's fact-c