skill-debate

Orchestrates structured multi-round debates between Claude and external AI provider CLIs with synthesis.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill skill-debate-gongyuancaiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-debate
Source: https://github.com/GongYuanCaiJi/dsh-claude-octopus/tree/main/.claude/skills/skill-debate
Command: npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill skill-debate-gongyuancaiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Critical technical decisions made from a single AI model's perspective risk blind spots and groupthink. This Skill runs structured multi-round debates where Claude, Sonnet, and external provider CLIs (Codex, Antigravity, Copilot, Qwen, Grok) independently analyze a question, challenge each other across rounds, and converge into a synthesized recommendation. ## Core Features & Use Cases - Multi-Provider Debate Rounds: Dispatches advisors through orchestrate.sh for 1-10 rounds in quick, thorough, adversarial, or collaborative styles, with quality scoring on each response. - Moderated Synthesis: Claude acts as both participant and moderator, writing independent analysis each round and producing a final synthesis with agreements, disagreements, and recommended next steps. - Session-Aware Artifacts: Saves context.md, per-round responses, state.json, and synthesis.md to a session-scoped debate folder, with optional deliverable generation via --synthesize. - Use Case: Before choosing between Redis and in-memory caching, run a 3-round adversarial debate so Codex, Antigravity, and Sonnet each argue trade-offs, then receive a synthesized decision record. ## Quick Start Ask the assistant to run a debate on whether your team should adopt GraphQL or REST for the new API, with three rounds and a synthesized recommendation.

Frequently Asked Questions about skill-debate

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

FAQPage Schema
How do I run a multi-model AI debate on a technical decision?▼

Invoke the debate with a question such as "/octo:debate Should we use Redis or in-memory cache?". The skill checks provider availability, dispatches external advisors like Codex and Antigravity through orchestrate.sh, adds Sonnet and Claude analyses, and synthesizes all perspectives.

What debate styles and rounds does the skill support?▼

Four styles are supported: quick (1 round), thorough (3 rounds), adversarial (3 rounds), and collaborative (2 rounds). You can override rounds with -r/--rounds from 1 to 10, and an explicit --rounds value always takes precedence over style defaults.

Which AI providers can participate in a debate?▼

Participants are selected at runtime from installed providers including Codex, Antigravity (agy), Copilot, Qwen, and Grok, plus Sonnet via the Agent tool and Claude as moderator. The build-fleet.sh helper picks up to three debaters from different model families for diversity.

What happens if no external AI provider CLI is installed?▼

The skill runs check-providers.sh before starting and reports each provider's real availability. If all external providers are missing, it tells you a debate needs at least one external provider and suggests running /octo:setup to configure them.

Where are debate results saved and can I export them?▼

Each debate is stored in a session-scoped folder under ~/.claude-octopus/debates containing context.md, per-round response files, state.json, and synthesis.md. Results can be exported to PPTX, DOCX, or PDF through the document-delivery skill.

How does the skill prevent low-quality advisor responses?▼

Every advisor response is scored out of 100 on length, citations, code examples, and engagement with other advisors' points. Scores below 50 trigger a re-prompt for elaboration, while scores of 50-74 proceed with a warning flagged in the synthesis.