What problem does it solve? Single-reviewer code reviews miss edge cases and suffer from individual blind spots, letting bugs slip into production. This protocol launches two independent blind judge sub-agents in parallel against the same target, synthesizes their findings, applies fixes, and re-judges until both pass or the user escalates. ## Core Features & Use Cases - Parallel Blind Review: Two judge sub-agents review the same target independently via async delegation, with no cross-contamination, then the orchestrator synthesizes confirmed, suspect, and contradictory findings into a verdict table. - Warning Classification & Convergence: Findings are split into CRITICAL, real WARNING, theoretical WARNING, and SUGGESTION, with a convergence threshold that stops diminishing-returns re-judge cycles after Round 1. - Fix and Re-judge Loop: A separate Fix Agent applies only confirmed issues, then fresh judges re-review; after 2 iterations the user decides whether to continue or escalate. - Use Case: Before merging a significant feature, ask for a judgment day review so two adversarial reviewers independently hunt for correctness, security, performance, and convention issues, then confirmed bugs are fixed and re-verified automatically. ## Quick Start Ask the agent to run judgment day on the specific files or feature you want reviewed before merging.