/debate
AI Debate Hub - Structured debates across Claude and available external providers
> /plugin marketplace add nyldn/claude-octopus
Command definition
debate.mdcommand: debate
disable-model-invocation: true
description: "AI Debate Hub - Structured debates across Claude and available external providers"
skill: skill-debate
Debate
Load `skills/blocks/engineering-method-selection.md` from the installed plugin and apply only the methods relevant to this task. Preserve this entry point's execution contract and output format. Read referenced skills as instructions; do not invoke the current command recursively or add provider calls from a seat.
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.**
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"}
]
}
]
})Read more
command: debate disable-model-invocation: true description: "AI Debate Hub - Structured debates across Claude and available external providers" skill: skill-debate
Debate
Load `skills/blocks/engineering-method-selection.md` from the installed plugin and apply only the methods relevant to this task. Preserve this entry point's execution contract and output format. Read referenced skills as instructions; do not invoke the current command recursively or add provider calls from a seat.
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.**
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"}
]
}
]
})Every AI model has blind spots. Claude Octopus supports twelve external provider integrations — Codex, Antigravity CLI, Copilot, Qwen, Ollama, Perplexity, OpenRouter, OrcaRouter, OpenCode, Cursor CLI, Grok, and Kimi Code — alongside the built-in Claude Code
Other commands on octo.
More commands from other plugins.
setup
CommandOne-time setup after installing ARIS as a Claude Code plugin — registers the Codex reviewer MCP server from the plugin directory…
autoresearch
CommandAutonomous iteration loop: modify, verify, keep/discard against any metric
agent
Commandname: sc:agent description: SC Agent — session controller that orchestrates investigation, implementation, and review category:…

