skill-parallel-agents
Decompose large tasks across parallel agents — use for migrations, multi-file refactors, or batch work
git clone --depth 1 https://github.com/nyldn/claude-octopus /tmp/skill-parallel-agents && cp -r /tmp/skill-parallel-agents/.claude/skills/skill-parallel-agents ~/.claude/skills/skill-parallel-agentsSKILL.md
# 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"
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh grasp "Define auth requirements"
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh tangle "Implement auth feature"
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh ink "Validate and deliver auth implementation"
# Crossfire: Adversarial cross-model review
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh grapple "implement password reset API"
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh grapple --principles security "implement JWT auth"
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh squeeze "review auth.ts for vulnerabilities"
# Smart auto-routing (detects intent automatically)
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh auto "research OAuth patterns" # -> probe
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh auto "build user login" # -> tangle + ink
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh auto "review the auth code" # -> ink
```
## IMPORTANT: When NOT to Use This Skill
**DO NOT use this skill if the user's request involves:**
1. **Built-in Claude Code commands** - Commands starting with `/` that are part of Claude Code itself:
- `/plugin` - Plugin management (add, remove, update, list)
- `/init` - Project initialization
- `/help` - Help documentation
- `/clear` - Clear conversation
- `/commit` - Git commit operations
- `/remember` - Memory management
- Any other `/` command that isn't `/parallel-agents` or `/octo:*`
2. **Direct tool usage** - Simple file operations, git commands, or terminal tasks
- Reading/writing files
- Running git commands
- Basic bash operations
- These should use built-in tools directly
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:
| Indicator | Meaning | Uses |
|-----------|---------|------|
| 🐙 | **Parallel Mode** | Multiple CLIs orchestrated via orchestrate.sh |
| 🔴 | **Codex CLI** | OpenAI Codex (your OPENAI_API_KEY) |
| 🧭 | **Antigravity CLI** | Google Antigravity (your authenticated seat) |
| 🔵 | **Claude Subagent** | Claude Code Task tool (built-in) |
### What Triggers External CLIs vs Subagents
**External CLIs execute when:**
- Using `/parallel-agents` command explicitly
- Using `/octo:debate` command (AI Debate Hub)
- Running orchestrate.sh workflows (probe, grasp, tangle, ink, embrace, grapple, squeeze)
- 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, 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 TriggerBackend 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.