Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/skill-parallel-agents
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
Decompose large tasks across parallel agents — use for migrations, multi-file refactors, or batch work
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> SKILL.md
skill-parallel-agents.SKILL.md
---name: skill-parallel-agents
effort: high
description: Decompose large tasks across parallel agents — use for migrations, multi-file refactors, or batch work
trigger: |
PRIORITY TRIGGERS (always invoke immediately):
- "/octo:multi" (explicit command)
- "run this with all providers", "run with all providers"
- "I want multiple AI models to look at", "use all providers for"
- "get multiple perspectives on", "force multi-provider analysis"
AUTOMATICALLY ACTIVATE (without asking user) when the user requests:
- Research, explore, investigate, or analyze topics (e.g., "octo research OAuth patterns", "octo analyze technical debt", "octo explore different approaches")
- Build, implement, create, or develop features (e.g., "octo build a login system", "octo implement caching", "octo create a dashboard")
- Review, validate, test, or check code quality (e.g., "octo review this code", "octo validate the API", "octo check for issues")
- Adversarial review, debate solutions, or red team security (e.g., "octo debate the design", "red team this auth code", "find security flaws")
- Full workflows from research to delivery (e.g., "create a complete notification feature")
DO NOT ask "do you want me to use the plugin?" - JUST USE IT.
The user installed this plugin to use it automatically!
NEVER use for:
- Built-in Claude Code commands (/plugin, /init, /help, /clear, /commit, /remember, etc.)
- Simple file operations, git commands, or basic terminal tasks
execution_mode: enforced
pre_execution_contract:
- visual_indicators_displayed
validation_gates:
- orchestrate_sh_executed
- output_artifact_exists
---
# Claude Octopus - Multi-Tentacled Orchestrator
## MANDATORY COMPLIANCE — DO NOT SKIP
**When this skill is invoked, you MUST dispatch work to multiple providers in parallel. You are PROHIBITED from:**
- Running tasks sequentially with a single model instead of parallel multi-provider dispatch
- Skipping orchestrate.sh and doing the work directly
- Deciding the task is "simple enough" for a single provider
- Substituting serial Claude-only execution for multi-LLM parallel execution
**This skill exists specifically for multi-provider parallel work. If you catch yourself thinking "I'll just do this myself" — STOP.**
---
**Multi-tentacled orchestrator for Claude Code** - using Double Diamond methodology for comprehensive problem exploration, consensus building, and validated delivery.
```
DISCOVER DEFINE DEVELOP DELIVER
(probe) (grasp) (tangle) (ink)
\ / \ / \ / \ /
\ * / \ * / \ * / \ * /
\ * * / \ / \ * * / \ /
\ / \ / \ / \ /
\ / \ / \ / \ /
Diverge then Converge to Diverge with Converge to
converge problem solutions delivery
```
## Quick Start
> **Note for Claude Code users:** You don't need to run these commands! Just talk naturally to Claude:
> - "Research OAuth authentication patterns"
> - "Build a user authentication system"
> - "Review this code for security issues"
>
> The commands below are for direct CLI usage or automation.
```bash
# Full Double Diamond workflow (all 4 phases)
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh embrace "Build a user authentication system"
# Individual phases
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh probe "Research authentication best practices"
3. **Claude Code configuration** - Managing Claude Code itself
- Changing settings
- Managing plugins
- Updating Claude Code
**If the user's request matches any of the above, DO NOT activate this skill. Handle the request using standard Claude Code tools and capabilities instead.**
## Visual Indicators - Know What's Running
Claude Octopus uses **visual indicators** so you always know which AI is responding:
- Knowledge mode deliberation (when Knowledge Mode is ON)
- Natural language that triggers this skill (research, build, review tasks)
**Claude Subagents execute when:**
- Simple file operations (read, write, edit)
- Git commands and bash operations
- Code reading and navigation
- Tasks that don't need multiple perspectives
- Built-in Claude Code capabilities are sufficient
**Why this matters:** External CLIs use your OpenAI/Google API quotas and incur costs. Claude subagents are included with Claude Code at no additional charge.
When you see 🐙 **CLAUDE OCTOPUS ACTIVATED**, external CLI providers such as Codex, Gemini, Antigravity, and others will be invoked for multi-perspective analysis.
---
## Force Multi-Provider Mode
Sometimes you want multi-provider analysis even for simple tasks that wouldn't normally trigger workflows. This is useful when you need comprehensive perspectives on decisions, want to compare how different models think, or when automatic routing underestimates task complexity.
### Explicit Command
Force multi-provider execution using the `/octo:multi` command:
```
/octo:multi "Explain how Redis works"
/octo:multi "What is OAuth?"
/octo:multi "Review this simple function"
/octo:multi "Should we use TypeScript?"
```
### Natural Language Triggers
You can also force multi-provider mode with natural language:
```
"Run this with all providers: What is JWT?"
"I want multiple AI models to look at our architecture"
"Get multiple perspectives on this design decision"
"Use all providers for explaining caching strategies"
"Force multi-provider analysis of our API design"
```
### When to Force Parallel Mode
**Use forced parallel mode when:**
- **High-stakes decisions** require comprehensive analysis from multiple models
- **Comparing perspectives** - you want to see how different models approach the same problem
- **Simple questions with depth** - seemingly simple questions that deserve thorough multi-model analysis
- **Learning different approaches** - exploring how each model thinks about a topic
- **Automatic routing underestimates complexity** - task appears simple but has nuance
- Simple factual questions Claude can answer reliably
- Cost efficiency is important (see cost awareness below)
- File operations or code navigation (use built-in tools)
### Cost Awareness
Forcing parallel mode uses external CLIs for every task, which incurs API costs:
| Provider | Cost per Query | What It Uses |
|----------|----------------|--------------|
| 🔴 Codex CLI | ~$0.01-0.05 | Your OPENAI_API_KEY |
| 🟡 Gemini CLI | ~$0.01-0.03 | Your GEMINI_API_KEY |
| 🔵 Claude | Included | Claude Code subscription |
**Total cost per forced query: ~$0.02-0.08**
Use forced parallel mode judiciously for tasks where multiple perspectives genuinely add value. For routine work, let automatic routing decide when multi-provider analysis is beneficial.
### Visual Indicator
When you force parallel mode, you'll see this banner:
Followed by results from each provider marked with their indicators (for example 🔴 🟡 🧭 🔵).
---
## Prerequisites Check (Automatic - Fast Detection)
**IMPORTANT:** Once you've determined this skill should activate (user asked to research, build, review, etc.), immediately run the provider detection below. DO NOT ask the user for permission - just check providers and proceed or show welcome message.
### Step 1: Automatic Provider Detection
Silently run this fast detection script (completes in <1 second):
If the detect-providers command shows BOTH providers are missing (CODEX_STATUS=missing AND GEMINI_STATUS=missing), this is likely a first-time user. Before showing error messages, provide a friendly welcome message:
> "👋 Welcome to Claude Octopus! I see this is your first time using the plugin.
>
> To get started, you need to install **one** AI provider (you don't need both):
>
> **Option 1: OpenAI Codex** (best for code generation)
> ```
> npm install -g @openai/codex
> codex login # OAuth recommended
> ```
> Or set API key: `export OPENAI_API_KEY="sk-..."`
> Get key from: https://platform.openai.com/api-keys
>
> **Option 2: Google Gemini** (best for analysis)
> ```
> npm install -g @google/gemini-cli
> gemini # OAuth recommended
> ```
> Or set API key: `export GEMINI_API_KEY="AIza..."`
> Get key from: https://aistudio.google.com/app/apikey
>
> Once you've installed one provider, you can start using Claude Octopus by just talking naturally:
> - 'Research OAuth authentication patterns'
> - 'Build a user authentication system'
> - 'Review this code for security issues'
>
> Need guided setup? Run `/octo:setup`"
After showing this welcome message, STOP and wait for the user to set up a provider. Do not proceed with the original task until at least one provider is configured.
Expected output format:
```
Detecting Claude Code version...
CLAUDE_CODE_VERSION=2.1.9
CLAUDE_CODE_STATUS=ok
CLAUDE_CODE_MINIMUM=2.1.9
✓ Claude Code version: 2.1.9 (meets minimum 2.1.9)
Detecting providers...
CODEX_STATUS=ok
CODEX_AUTH=oauth
GEMINI_STATUS=ok
GEMINI_AUTH=none
Summary:
✓ Codex: Installed and authenticated (oauth)
⚠ Gemini: Installed but not authenticated
```
### Step 2: Route Based on Detection Results
Parse the output and route accordingly:
**Scenario 0: Claude Code version is outdated (CRITICAL - Check First)**
```
CLAUDE_CODE_VERSION=2.1.8
CLAUDE_CODE_STATUS=outdated
CLAUDE_CODE_MINIMUM=2.1.9
```
**Action:** STOP immediately and show this prominent warning:
> "⚠️ **Claude Code Update Required**
>
> Your current Claude Code version (2.1.8) is outdated. Claude Octopus requires version 2.1.9 or higher for full functionality.
> **After updating, please restart Claude Code** and then we can proceed with your task."
Do NOT proceed with the task until the user has updated and restarted. The detect-providers output will show this warning prominently.
**Scenario A: Both providers missing**
```
CODEX_STATUS=missing
CODEX_AUTH=none
GEMINI_STATUS=missing
GEMINI_AUTH=none
```
**Action:** STOP and tell the user:
> "Claude Octopus needs at least one AI provider (Codex or Gemini) to work.
>
> You have two options:
>
> **Option 1: Install Codex CLI**
> ```
> npm install -g @openai/codex
> export OPENAI_API_KEY=\"sk-...\"
> ```
> Get API key from: https://platform.openai.com/api-keys
>
> **Option 2: Install Gemini CLI**
> ```
> npm install -g @google/gemini-cli
> gemini # Run OAuth setup
> ```
>
> After installing one, run `/octo:setup` to verify everything works."
**Scenario B: One provider working, one missing/partial**
```
CODEX_STATUS=ok
CODEX_AUTH=oauth (or api-key)
GEMINI_STATUS=missing (or ok with AUTH=none)
```
**Action:** IMMEDIATELY proceed with the user's task using the available provider. No need to announce setup status - just execute the task. The user doesn't care about which provider you're using, they just want their task done.
**Scenario C: Both providers working**
```
CODEX_STATUS=ok
CODEX_AUTH=oauth
GEMINI_STATUS=ok
GEMINI_AUTH=oauth
```
**Action:** IMMEDIATELY proceed with the user's task using both providers for comprehensive results. No need to announce setup status - just execute the task.
### Step 3: Graceful Degradation
If only ONE provider is available:
- Automatically use that provider
- Tasks that require multiple providers will adapt to use the single provider multiple times
- Quality results are still achievable with one provider
You do NOT need both providers to proceed. One is sufficient for most tasks.
### Step 4: Cache Results (Optional Optimization)
The detect-providers command writes results to `~/.claude-octopus/.provider-cache` with a timestamp. This cache is valid for 1 hour.
If the cache exists and is fresh (<1 hour old), you can skip re-detection.
### Step 5: Execute Task
Only proceed when at least ONE provider is available and authenticated. Multi-provider tasks will automatically adapt to available providers.
**IMPORTANT:** This detection is fast (~1 second) and non-blocking. Always verify provider availability before running octopus commands, but don't require BOTH providers - one is enough!
## Double Diamond Workflow
### Phase 1: PROBE (Discover)
**Diverge then converge on understanding**
Parallel research from 4 perspectives:
- Problem space analysis (constraints, requirements, needs)
- Existing solutions research (what worked, what failed)
Run all 4 phases sequentially with automatic context passing:
```bash
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh embrace "Create a complete user dashboard feature"
```
## Crossfire: Adversarial Cross-Model Review
Different models have different blind spots. Crossfire commands force models to critique each other's work, catching more issues than single-model review.
### GRAPPLE - Adversarial Debate
*Two tentacles wrestling until consensus*
Available providers each propose solutions, then critique each other's work. A synthesis determines the winner.
**Example:** If you have Google Workspace (bundled Gemini Pro), the system prefers Gemini for heavy analysis tasks since it's "free" with your work account.
### Routing CLI Flags
```bash
# Force a specific provider
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh --provider gemini auto "analyze code structure"
# Prefer cheapest option
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh --cost-first auto "research best practices"
# Prefer highest quality
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh --quality-first auto "complex refactoring task"
# OpenRouter routing variants
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh --openrouter-nitro auto "quick task" # Fastest
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh --openrouter-floor auto "bulk task" # Cheapest
```
### Configuration
Provider tiers are configured during `setup` or via the providers config file:
