debate
The `/debate` command orchestrates structured four-way debates between Claude, Sonnet, Gemini, and Codex on user-specified topics. Use this when you need multiple AI perspectives on a question, want comparative argumentation across different models, or require a synthesized analysis that considers diverse reasoning approaches before making decisions.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/nyldn/claude-octopus/HEAD/commands/debate.md -o ~/.claude/commands/debate.mddebate.md
# Debate
Structured AI debates between Claude and available external providers such as Codex, Antigravity, Grok, OpenCode, and OpenRouter.
## 🤖 INSTRUCTIONS FOR CLAUDE
### MANDATORY COMPLIANCE — DO NOT SKIP
**When the user explicitly invokes `/octo:debate`, you MUST execute the structured debate workflow below.** You are PROHIBITED from answering the question directly, skipping the multi-provider debate, or deciding the topic is "too simple" for a provider debate. The user chose this command deliberately — respect that choice.
### EXECUTION MECHANISM — NON-NEGOTIABLE
**You MUST dispatch work to external providers (Codex, Antigravity, Grok, etc.) for this command. You are PROHIBITED from:**
- ❌ Executing the entire task using only Claude-native tools
- ❌ Using a single Agent subagent instead of multi-provider dispatch
- ❌ Skipping provider dispatch because "I can handle this alone"
**Multi-LLM orchestration is the purpose of this command.** Single-model execution defeats its purpose.
---
### Execution
1. Follow the `skill-debate` instructions (Steps 1-7) exactly.
2. Start with Step 1: check provider availability and display the visual indicator banner.
3. Step 2: ask clarifying questions via AskUserQuestion before proceeding.
4. Steps 3-5: parse arguments, set up debate folder, conduct rounds with the selected participants (for example Codex CLI, Antigravity CLI, Grok CLI, Sonnet Agent, Claude/Opus).
5. Steps 6-7: write final synthesis and present results to the user.
6. Apply quality gates and cost tracking from `skill-debate` throughout.
### Post-Completion — Interactive Next Steps
**CRITICAL: After the debate completes, you MUST ask the user what to do next. Do NOT end the session silently.**
```javascript
AskUserQuestion({
questions: [
{
question: "The debate is complete. What would you like to do next?",
header: "Next Steps",
multiSelect: false,
options: [
{label: "Run another round", description: "Continue the debate with additional rounds"},
{label: "Act on the winner", description: "Proceed with the winning argument's recommendation"},
{label: "Debate a related topic", description: "Start a new debate on a follow-up question"},
{label: "Export the synthesis", description: "Save the debate results as a document"},
{label: "Done for now", description: "I have what I need"}
]
}
]
})
```Backend architect. Delegate only when the user explicitly starts an Octopus workflow.
Cloud architect. Delegate only when the user explicitly starts an Octopus workflow.
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
Database architect. Delegate only when the user explicitly starts an Octopus workflow.
Debugger. Delegate only when the user explicitly starts an Octopus workflow.
Documentation architect. Delegate only when the user explicitly starts an Octopus workflow.
Frontend developer. Delegate only when the user explicitly starts an Octopus workflow.
Performance engineer. Delegate only when the user explicitly starts an Octopus workflow.