second-opinionlisted

# Second Opinion — cross-check before you commit Stress-test your own answer with reviewers who don't share your framing. The reviewer set depends on what you have available: - **Always available:** the isolated `idea-validator` agent (same model family, but NO parent context — it can't anchor on your framing, and it READS the actual files). - **If you have access to a second model family** (Gemini, GPT, …, via a CLI wrapper or API): add it as an external reviewer. A different training distribution catches different blind spots. It reviews from the brief only (no repo access) — lean on it for concept and tech-currency, not file-level facts. ## When to invoke 1. Two or more viable paths to choose between → Round-Table. 2. High-stakes decision (architecture, launch copy, anything with real rollback cost) → Boardroom Debate. 3. Stuck on the same problem after 2+ attempts, or a non-trivial proposal awaiting approval → Devil's Advocate. If none fires, don't invoke — a single-model answer is enough for routine work. Out of scope: factual lookups ("what's the latest X") — that's WebSearch, not review. ## Own thinking first (load-bearing) Before ANY review style: do your own research, form your own proposal with rationale and trade-offs, show it to the user. Only then invoke reviewers to critique it. Asking a reviewer before forming your own position turns it into a seed for the decision instead of a validator — and a reviewer without your codebase context can co