3-surgeons-marketplace

3-Surgeons

Three AI surgeons. One operating table. Your code doesn't ship until all three agree.

Would you wing a complicated surgery with one surgeon?

Then why are you shipping code reviewed by one AI?

The Problem

Every AI coding tool has the same flaw: one model, one perspective, one set of blind spots. Claude confabulates confidently where GPT hedges. GPT over-engineers where a local model stays lean. A single AI reviewer is a single point of failure — and you'd never accept that in a real operating room.

The Solution

3-Surgeons puts three independent AI models on the same operating table. They don't just review — they cross-examine, challenge assumptions, and hunt for what the others missed. Your code ships only when all three agree it's ready.

	Surgeon	Role	Default Model
🔪	Head Surgeon	Synthesizes, decides, implements	Claude (your IDE session)
🩺	Cardiologist	External perspective, cross-examination	GPT-4.1-mini (OpenAI)
🧠	Neurologist	Pattern recognition, corrigibility checks	Qwen3-4B (local, private)

Why It Works: Corrigibility

Most AI tools optimize for confidence. 3-Surgeons optimizes for correctness.

The core principle: no surgeon can conclude an opinion until an objective test of the opposing view yields legitimate data — only then is the opinion merited.

This isn't just "get a second opinion." It's an iterative consensus loop:

1. Each surgeon hunts independently — different prompts, different search strategies, different biases
2. Cross-examination — each surgeon reviews the others' findings and challenges weak points
3. Open exploration — "What are we ALL blind to? What assumptions remain unchallenged?"
4. Consensus only when saturated — disagreements are preserved, not suppressed

Feel the difference between code that was generated and code that survived.

The 4-Phase Operating Protocol

┌─────────────┐    ┌──────────────┐    ┌─────────────┐    ┌───────────┐
│  1. TRIAGE   │───▶│  2. OPERATE   │───▶│  3. REVIEW   │───▶│  4. CLOSE  │
│  Assess risk │    │  Independent  │    │  Cross-exam  │    │  Consensus │
│  Set gates   │    │  analysis     │    │  Challenge   │    │  or dissent│
└─────────────┘    └──────────────┘    └─────────────┘    └───────────┘

Triage — Sentinel scans your change for complexity vectors and calibrates review intensity. Operate — Each surgeon analyzes independently. No groupthink. Review — Cross-examination. Each surgeon attacks the others' blind spots. Close — Consensus with confidence scores. Disagreements surfaced, never hidden.

Blast Radius Calibration

Not every change needs a full surgery. 3-Surgeons adapts review intensity to risk:

Risk Level	Gate Intensity	When	Time
Light	Sentinel scan only	Docs, config, cosmetic changes	<30s
Standard	Sentinel + cross-exam + gains-gate	Feature work, refactors	<120s
Full	All gates + counter-position + A/B	Architecture, security, schema, API changes	<300s

Risk is measured across blast radius, reversibility, security exposure, data impact, and external coupling. The highest-risk dimension determines the gate.

Prerequisites

Python 3.10+ is required for the MCP server (cross-examination tools in your IDE).

# Check your version
python3 --version

# If below 3.10, install via Homebrew (macOS)
brew install python@3.12

# Or via pyenv (any platform)
pyenv install 3.12
pyenv global 3.12

The 3s init wizard will check your Python version and guide you if it's too old.

Quick Start

# 1. Install (Claude Code)
/plugin marketplace add supportersimulator/3-surgeons
/plugin install 3-surgeons@supportersimulator/3-surgeons

# 2. Run the setup wizard
3s init

# 3. Set your API key(s)
export OPENAI_API_KEY=sk-...

# 4. Verify all surgeons are reachable
3s probe

# 5. Your first cross-examination
3s cross-exam "Should we use Redis or PostgreSQL for session storage?"

Install

Claude Code (Marketplace)

/plugin marketplace add supportersimulator/3-surgeons
/plugin install 3-surgeons@supportersimulator/3-surgeons

VS Code (Agent Plugin — requires 1.110+)

Important: This uses VS Code's Agent Plugin system (Chat panel), NOT the traditional Extension Marketplace. You will NOT find it by searching in the Extensions sidebar.

Step 1: Install GitHub Copilot Chat

Install the GitHub Copilot Chat extension from the VS Code Marketplace (not the legacy "GitHub Copilot" extension). Sign into GitHub with a Copilot-entitled account.

Step 2: Enable plugins and add the marketplace

Open Settings (Cmd+, / Ctrl+,) and add these to your settings.json:

{
  "chat.plugins.enabled": true,
  "chat.plugins.marketplaces": ["supportersimulator/3-surgeons"]
}