octo-multi

Multi - Multi-Provider Override

Forces multi-provider execution for any task using all available AI providers.

🤖 INSTRUCTIONS FOR CLAUDE

EXECUTION MECHANISM — NON-NEGOTIABLE

You MUST dispatch work to external providers (Codex, Gemini, 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.

When the user invokes this command (e.g., /octo:multi <task>):

Step 1: Cost Awareness & Intent Confirmation

CRITICAL: Before forcing multi-provider execution, use AskUserQuestion to confirm intent and cost awareness:

AskUserQuestion({
  questions: [
    {
      question: "Why do you need multiple AI perspectives?",
      header: "Intent",
      multiSelect: false,
      options: [
        {label: "High-stakes decision", description: "Critical choice requiring comprehensive analysis"},
        {label: "Quality validation", description: "Cross-check important work for accuracy"},
        {label: "Learning different approaches", description: "See how different models think"},
        {label: "Comparing perspectives", description: "Want to see model-specific insights"},
        {label: "Just exploring", description: "Curious about multi-AI capabilities"}
      ]
    },
    {
      question: "Are you aware this uses external API credits?",
      header: "Cost",
      multiSelect: false,
      options: [
        {label: "Yes, proceed (~$0.02-0.08/query)", description: "I understand this costs money via Codex + Gemini APIs"},
        {label: "Tell me more about costs", description: "Explain what I'll be charged"},
        {label: "Use free providers only", description: "Skip Codex/Gemini, use Claude only"}
      ]
    }
  ]
})

WAIT for the user's answers before proceeding.