By agent-sh
Structured multi-round debate between AI tools with proposer/challenger roles and verdict
Structured multi-round debate between two AI tools - one proposes, one challenges, and an orchestrator delivers a verdict.
A single AI tool gives you one perspective. When the stakes are high - architecture decisions, schema design, migration strategies - you want adversarial pressure-testing. debate pits two AI tools against each other in a structured format with enforced rules: the challenger must find flaws before agreeing, both sides must cite evidence, and the orchestrator must pick a winner.
Use cases:
agentsys install debate
Requires at least two AI CLI tools installed. See consult for individual tool install commands.
# Codex argues for, Gemini challenges - 2 rounds about microservices
/debate codex vs gemini about microservices vs monolith
# Thorough 3-round debate with explicit flags
/debate "Should we use event sourcing?" --tools=claude,gemini --rounds=3 --effort=high
# Include the current git diff as context for both tools
/debate codex vs gemini about this refactoring approach --context=diff
The challenger operates under adversarial rules - it must lead with what is wrong or missing before acknowledging agreements, and cannot agree with unsupported claims.
/debate codex vs gemini about microservices vs monolith
/debate with claude and codex about our auth implementation
/debate thoroughly gemini vs codex about database schema design
/debate codex vs gemini 3 rounds about event sourcing
/debate "Redis vs PostgreSQL for caching" --tools=codex,opencode
/debate "Should we use event sourcing?" --tools=claude,gemini --rounds=3 --effort=high
/debate "Performance optimization" --tools=codex,gemini --context=diff
| Flag | Values | Default | Description |
|---|---|---|---|
--tools | TOOL1,TOOL2 | interactive | Proposer and challenger (comma-separated) |
--rounds | 1-5 | 2 | Number of back-and-forth exchanges |
--effort | low, medium, high, max | interactive | Reasoning depth for both tools |
--context | diff, file=PATH, none | none | Codebase context shared with both tools |
--model-proposer | any model identifier | from effort | Override proposer model |
--model-challenger | any model identifier | from effort | Override challenger model |
Each debate produces a structured result:
MIT
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Professional-grade slash commands for Claude Code with cross-platform support
Lint agent configuration files (SKILL.md, CLAUDE.md, hooks, MCP) against 414 rules across 10+ AI tools
Find where to contribute to any project - matches developer skills to test gaps, stale docs, bugspots, and open issues
Deep repository analysis to realign project plans with actual code reality - discovers drift, gaps, and produces prioritized reconstruction plans
Master workflow orchestrator with autonomous task-to-production automation, quality gates, and multi-agent review
npx claudepluginhub agent-sh/debate --plugin debateMulti-agent deliberation for AI coding assistants
Multi-agent council orchestration via Claude Code agent teams.
Debate implementation approaches with structured pros and cons analysis
Convene parallel role-specialized peer agents (dynamic roster, plan card first) to debate a cross-domain decision or audit a codebase in real time. Invoking Claude acts as CEO: convenes, routes peer-DMs, arbitrates deadlocks, writes a one-page decision log.
Use when you want a delegated second opinion or implementation from GPT (Codex), Gemini, Grok (xAI), or OpenRouter (config-driven, 400+ models) - seven expert subagents (Architect, Plan Reviewer, Scope Analyst, Code Reviewer, Security Analyst, Researcher, Debugger) and bundled ask-gpt/ask-gemini/ask-grok/ask-openrouter/ask-all/consensus commands, advisory (read-only) or implementation (write; Grok and OpenRouter are advisory-only).
Harness-native ECC plugin for engineering teams - 67 agents, 279 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses