Claude Code Teams
Skill by matthew-a-gordon
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/matthew-a-gordon/claude-code-teamsname: claude-code-teams description: Production skill for orchestrating Claude Code's native agent teams feature. Use when: (1) Multi-lens reviews, (2) Competing hypotheses debugging, (3) Full-stack features, (4) Architecture debates, (5) Cross-domain investigations. metadata: openclaw: emoji: "🎭" requires: bins: ["claude"] env: ["CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS"] version: "1.0.0" author: "Matthew Gordon" tags: ["agents", "teams", "claude-code", "orchestration", "coordination"]
Claude Code Agent Teams
Orchestrate multiple Claude Code agents working together on complex tasks. Agents coordinate through a shared task list, message each other directly, and work in parallel on independent scopes.
When to Use
✅ Use for parallel independent work:
- Multi-lens code reviews (security, performance, tests in parallel)
- Debugging with competing hypotheses (test theories simultaneously)
- Full-stack features (frontend/backend/tests by separate specialists)
- Architecture decisions (adversarial debate produces stronger ADRs)
- Cross-domain investigations (bottleneck analysis across systems)
- Data-parallel work (inventory classification, bulk refactoring)
❌ Don't use for:
- Sequential work with tight dependencies
- Same-file edits (conflict risk)
- Simple tasks (coordination overhead > benefit)
- Learning/exploration (single agent with full context is better)
Rule of thumb: Teams multiply token cost 3-4x. Use only when parallelization benefit exceeds coordination overhead.
Quick Start
1. Enable Feature
Environment variable:
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Or settings file (~/.claude/settings.json):
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
2. Validate Setup
./scripts/validate-setup.sh
Checks for: env var set, claude CLI available, tmux installed (optional).
3. Pick Template
| Template | Use Case |
|---|---|
parallel-review.md | Multi-lens code review (security + performance + tests) |
competing-hypotheses.md | Debug by testing competing theories |
fullstack-feature.md | Frontend/backend/tests coordination |
architecture-decision.md | ADR with adversarial debate |
bottleneck-analysis.md | Cross-domain performance investigation |
inventory-classification.md | Data-parallel classification/refactoring |
Each template includes: when to use, team structure, copy-paste spawn prompt, expected outcomes.
4. Spawn Team
claude --pty
# Paste spawn prompt from template
Monitor with ./scripts/team-monitor.sh (separate terminal) or Ctrl+T (in Claude Code).
Core Principles
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-matthew-a-gordon-claude-code-teams": {
"enabled": true,
"auto_update": true
}
}
}