skills/multi-brain-debate/SKILL.md
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.
npx skillsauth add fatih-developer/fth-skills multi-brain-debateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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
Same as base multi-brain. Ask one clarifying question if needed, otherwise proceed.
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]
Each instance can now see the others' positions and must:
## ⚔️ 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]
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]
Mandatory: The final response must include both debate rounds, the verdict, and the complete deliverable. The user must see the full reasoning trail.
| Situation | Use | |-----------|-----| | High-stakes architecture decision | Debate | | Choosing between competing technologies | Debate | | Quick implementation question | Base multi-brain | | Strategy with long-term consequences | Debate | | Simple feature decision | Base multi-brain | | Security-sensitive design | Debate |
references/EXAMPLES.md for worked debate examples.tools
Create, optimize, critique, and structure prompts for AI systems. Use this skill whenever the user is designing or improving a prompt, system prompt, coding prompt, image prompt, evaluation rubric, agent prompt, workflow prompt, or MCP-oriented prompt package. Also use it when the user asks to turn vague AI behavior into a precise instruction set, tool policy, agent spec, or prompt architecture.
testing
Assumption-first architecture review skill to stress-test project plans and expose hidden risks.
testing
Enforce and manage DESIGN.md specifications, extract design systems from URLs, and combine design reasoning with token roles to prevent drift.
testing
Forces the agent to act with a Claude-like product mindset, prioritizing user journey, UX states, and visual quality before coding.