Multi-Provider Adversarial Review

When to Use

Per AI Review Routing Policy:

• Two-provider (Codex): default for non-trivial plans and code
• Three-provider (Codex + Gemini): architecture-heavy, security-affecting, cross-module, high-stakes, ambiguous requirements, or context-saturated

Two Review Checkpoints

The user expects adversarial review at BOTH stages — not just implementation:

1. Checkpoint 1 — Plan review: before any implementation begins
2. Checkpoint 2 — Implementation review: before closing the issue / merging the PR

Do NOT skip the plan review. Do NOT defer all review to implementation.

Step 1: Prepare Review Material