debate

Run structured multi-agent adversarial debates with configurable formats and verdict generation.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill debate-tmalcolm-0607
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debate
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/debate
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill debate-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Single-perspective analysis of ideas and decisions has inherent blind spots that can lead to unexamined assumptions, overlooked trade-offs, and flawed conclusions. This Skill eliminates that risk by enabling structured, multi-agent adversarial debate that forces rigorous defense of positions against direct challenges.

Core Features & Use Cases

  • 4 Configurable Debate Formats: Choose from adversarial panel, Oxford, fishbowl, or devil's advocate formats optimized for different decision types, from binary go/no-go calls to open-ended design choices.
  • 6 Panel Compositions: Select from pre-built panels (classic, technical, strategic, research, stakeholder) or create custom agent teams of up to 6 members to match your decision context.
  • User Interview Integration: Optionally inject stakeholder input between debate rounds to ground arguments in real-world constraints and domain expertise.
  • Formal Verdict Generation: Produces convergence maps, attack/defense analysis, and clear winner verdicts with explicit reasoning to support final decision-making.
  • Use Case Example: Use this Skill to evaluate whether to adopt event sourcing or CRUD for a new service, stress-test a microservices migration plan, or validate assumptions about a new product feature before committing resources.

Quick Start

Use the debate skill to run a structured adversarial debate on the question of whether to adopt microservices for your new platform, with a technical panel and 3 rounds of arguments.

Frequently Asked Questions about debate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does structured adversarial debate improve architecture design validation?▼

Structured adversarial debate improves architecture design validation by forcing multi-agent panels to rigorously defend positions against direct challenges, exposing blind spots and unexamined assumptions in single-perspective evaluations. It generates formal verdicts with convergence maps.

What is the best way to stress-test assumptions for a microservices migration plan?▼

The best way to stress-test microservices migration assumptions is running a structured multi-agent debate. You select a technical panel composition, choose a debate format like adversarial or devil's advocate, and review the generated attack/defense analysis to validate risks.

Can I integrate stakeholder input into a multi-agent debate for risk assessment?▼

Yes, you can integrate stakeholder input into risk assessment debates. The multi-agent debate process optionally injects user interview data between debate rounds to ground arguments in real-world constraints and domain expertise.

What debate formats are available for technology selection and decision-making?▼

Available debate formats for technology selection include adversarial panel, Oxford, fishbowl, and devil's advocate. These configurable formats optimize decision-making for different scenarios, ranging from binary go/no-go calls to open-ended design choices.

How do I configure panel compositions for an engineering decision evaluation?▼

You configure panel compositions for engineering decision evaluation by selecting from pre-built teams like classic, technical, strategic, research, or stakeholder panels. You can also create custom agent teams of up to 6 members to match your specific decision context.

When should I avoid using a devil's advocate format for design review?▼

You should avoid using the devil's advocate format for design review when your decision type requires open-ended design choices rather than binary go/no-go calls. Consider fishbowl or Oxford formats instead for collaborative exploration of complex architectural decisions.