multi-brain-debate

Two-round debate protocol where perspectives challenge each other before consensus. Round 1 presents independent positions, Round 2 allows counter-arguments and rebuttals. Produces battle-tested decisions for high-stakes choices.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "multi-brain-debate" with this command: npx skills add fatih-developer/fth-skills/fatih-developer-fth-skills-multi-brain-debate

Multi-Brain Debate Protocol

Extend the multi-brain consensus with a two-round adversarial debate. Perspectives don't just state their case — they challenge each other. The result is a stress-tested decision where weak arguments have been exposed and strong ones reinforced.


Workflow

1. Understand the request
2. Round 1: Independent positions (3 perspectives)
3. Round 2: Counter-arguments and rebuttals
4. Judge's verdict (consensus)
5. Produce full output with debate trail visible

Step 1: Understand the Request

Same as base multi-brain. Ask one clarifying question if needed, otherwise proceed.


Step 2: Round 1 — Opening Positions

Each instance presents their approach independently (same as base multi-brain):

## 🧠 Debate — Round 1: Opening Positions

**Instance A — Creative:**
[2-3 sentences: position + rationale]

**Instance B — Pragmatic:**
[2-3 sentences: position + rationale]

**Instance C — Comprehensive:**
[2-3 sentences: position + rationale]

Step 3: Round 2 — Challenges & Rebuttals

Each instance can now see the others' positions and must:

  1. Challenge the weakest point of another instance's argument
  2. Defend their own position against potential objections
## ⚔️ Debate — Round 2: Challenges

**A challenges B:**
[1-2 sentences: specific weakness identified]

**B challenges C:**
[1-2 sentences: specific weakness identified]

**C challenges A:**
[1-2 sentences: specific weakness identified]

**Rebuttals:**
- **A responds:** [1 sentence defense or concession]
- **B responds:** [1 sentence defense or concession]
- **C responds:** [1 sentence defense or concession]

Step 4: Judge's Verdict

After the debate, synthesize the strongest surviving arguments:

## ⚖️ Verdict

**Winner:** [Which perspective's core argument survived the debate]
**Incorporated from others:** [Elements from losing arguments that strengthen the decision]
**Eliminated:** [Arguments that were successfully challenged and dropped]

Step 5: Full Output

Mandatory: The final response must include both debate rounds, the verdict, and the complete deliverable. The user must see the full reasoning trail.


When to Use Debate vs Base Multi-Brain

SituationUse
High-stakes architecture decisionDebate
Choosing between competing technologiesDebate
Quick implementation questionBase multi-brain
Strategy with long-term consequencesDebate
Simple feature decisionBase multi-brain
Security-sensitive designDebate

Guardrails

  • Always show both rounds — the debate trail is the value, not just the verdict.
  • Challenges must be specific and substantive — not generic "this might not scale."
  • Rebuttals can include concessions — "You're right, I'll adjust my position to X."
  • The verdict must explain what was eliminated and why — not just what won.
  • Keep the total debate concise: Round 1 (2-3 sentences each), Round 2 (1-2 sentences each), Rebuttals (1 sentence each).
  • Do not force disagreement — if all 3 genuinely align, acknowledge it and skip Round 2.

References

  • See references/EXAMPLES.md for worked debate examples.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

task-decomposer

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

checkpoint-guardian

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

multi-brain-score

No summary provided by upstream source.

Repository SourceNeeds Review