debate
Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'.
agent-sh · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add agent-sh/agentsys --skill debateAbout this skill
name: debate description: "Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'." version: 5.1.0 argument-hint: "[topic] [--proposer=tool] [--challenger=tool] [--rounds=N] [--effort=level]"
debate
Prompt templates, context assembly rules, and synthesis format for structured multi-round debates between AI tools.
Arguments
Parse from $ARGUMENTS:
- topic: The debate question/topic (required)
- --proposer: Tool for the proposer role (claude, gemini, codex, opencode, copilot)
- --challenger: Tool for the challenger role (must differ from proposer)
- --rounds: Number of back-and-forth rounds (1-5, default: 2)
- --effort: Thinking effort applied to all tool invocations (low, medium, high, max)
- --model-proposer: Specific model for proposer (optional)
- --model-challenger: Specific model for challenger (optional)
Universal Rules
ALL participants (proposer AND challenger) MUST support claims with specific evidence (file path, code pattern, benchmark, or documented behavior). Unsupported claims from either side will be flagged by the other participant and noted in the verdict. This applies to every round.
Prompt Templates
Round 1: Proposer Opening
You are participating in a structured debate as the PROPOSER.
Topic: {topic}
Your job: Analyze this topic thoroughly and present your position. Take a clear stance. Do not hedge excessively.
You MUST support each claim with specific evidence (file path, code pattern, benchmark, or documented behavior). Unsupported claims will be challenged. "I think" or "generally speaking" without evidence is not acceptable.
Provide your analysis:
Round 1: Challenger Response
You are participating in a structured debate as the CHALLENGER.
Topic: {topic}
The PROPOSER ({proposer_tool}) argued:
---
{proposer_round1_response}
---
Your job: Find weaknesses, blind spots, and flaws in the proposer's argument. You MUST identify at least one genuine flaw or overlooked consideration before agreeing on anything. Propose concrete alternatives where you disagree.
Rules:
- Do NOT say "great point" or validate the proposer's reasoning before critiquing it
- Lead with what's WRONG or MISSING, then acknowledge what's right
- If you genuinely agree on a point, explain what RISK remains despite the agreement
- Propose at least one concrete alternative approach
- You MUST address at least these categories: correctness, security implications, and developer experience
- Do NOT agree with ANY claim unless you can cite specific evidence (file path, code pattern, or documented behavior) that supports the agreement. Unsupported agreement is not allowed.
- If the proposer makes a claim without evidence, call it out: "This claim is unsupported."
Provide your challenge:
Round 2+: Proposer Defense
You are the PROPOSER in round {round} of a structured debate.
Topic: {topic}
{context_summary}
The CHALLENGER ({challenger_tool}) raised these points in round {previous_round}:
---
{challenger_previous_response}
---
Your job: Address each challenge directly. For each point:
- If they're right, concede explicitly and explain how your position evolves
- If they're wrong, explain why with specific evidence (file path, code pattern, benchmark, or documented behavior)
- If it's a tradeoff, acknowledge the tradeoff and explain why you still favor your approach with evidence
Every claim you make -- whether concession, rebuttal, or new argument -- MUST cite specific evidence. The challenger will reject unsupported claims.
Do NOT simply restate your original position. Your response must show you engaged with the specific challenges raised.
Provide your defense:
Round 2+: Challenger Follow-up
You are the CHALLENGER in round {round} of a structured debate.
Topic: {topic}
{context_summary}
The PROPOSER ({proposer_tool}) responded to your challenges:
---
{proposer_previous_response}
---
IMPORTANT: Do NOT let the proposer reframe your challenges as agreements. If they say "we actually agree" but haven't addressed the substance, reject it. Default to suspicion, not acceptance.
Your job: Evaluate the proposer's defense. For each point they addressed:
- Did they dodge, superficially address, or respond without evidence? Call it out: "This defense is unsupported" or "This dodges the original concern"
- Did they concede any point? Hold them to it -- they cannot walk it back later without new evidence
- Are there NEW weaknesses in their revised position?
- Did they adequately address your concern with specific evidence? Only then acknowledge it, and cite what convinced you
You MUST either identify at least one new weakness or unresolved concern, OR explicitly certify a previous concern as genuinely resolved with specific evidence for why you're now satisfied. "I'm convinced because [evidence]" is acceptable. "I agree now" without evidence is not.
If you see new problems, raise them.
Provide your follow-up:
Context Assembly
Rounds 1-2: Full context
Include the full text of all prior exchanges in the prompt. Context is small enough (typically under 5000 tokens total).
Format for context block:
Previous exchanges:
Round 1 - Proposer ({proposer_tool}):
{full response}
Round 1 - Challenger ({challenger_tool}):
{full response}
Round 3+: Summarized context
For rounds 3 and beyond, replace full exchange text from rounds 1 through N-2 with a summary. Only include the most recent round's responses in full.
Format:
Summary of rounds 1-{N-2}:
{summary of key positions, agreements, and open disagreements}
Round {N-1} - Proposer ({proposer_tool}):
{full response}
Round {N-1} - Challenger ({challenger_tool}):
{full response}
The orchestrator agent (opus) generates the summary. Target: 500-800 tokens. MUST preserve:
- Each side's core position
- A