Templates and tooling for orchestrating parallel Claude Code agent teams
npm install claude-agent-teamsSet up and run parallel Claude Code sessions. One command.
``bash`
npx claude-agent-teams init
> Agent teams are experimental. Docs
Option 1: npx (no install)
`bash`
npx claude-agent-teams
Option 2: global install
`bash`
npm i -g claude-agent-teams
claude-agent-teams
Requires Node 16+ (you already have it if you use Claude Code).
Set up agent teams in your project. Installs a CLAUDE.md, enables the feature flag, and configures your display mode. Walks you through everything.
`bash`
npx claude-agent-teams init
npx claude-agent-teams init ./my-project
Skip the prompts with flags:
`bash`
npx claude-agent-teams init -y # defaults, no prompts
npx claude-agent-teams init --template=fullstack --mode=tmux # one-liner
npx claude-agent-teams init --template=monorepo --no-settings # skip settings
npx claude-agent-teams init --template=base --force # overwrite existing
| Flag | Values | Default |
|:---|:---|:---|
| --template | base, monorepo, fullstack, skip | base |--mode
| | auto, in-process, tmux | auto |--no-settings
| | — | writes to settings |--force
| | — | skips if exists |-y
| , --yes | — | interactive |
Browse all 30+ templates with descriptions. Every template tells you what it does and when to use it — no need to leave your terminal.
`bash`
npx claude-agent-teams list # everything
npx claude-agent-teams list prompts # just scenario prompts
npx claude-agent-teams list spawn-prompts # just role templates
npx claude-agent-teams list coordination # just coordination patterns
Preview any template before adding it — see what it contains, what sections it covers, and how to use it.
`bash`
npx claude-agent-teams info prompts/quickstart
npx claude-agent-teams info spawn-prompts/architect
npx claude-agent-teams info coordination/contract-first
Copy a template into your project. Shows contextual next steps after copying — different guidance for prompts, roles, CLAUDE.md, and coordination patterns.
`bash`
npx claude-agent-teams add prompts/quickstart # your first team
npx claude-agent-teams add prompts/code-review # parallel PR review
npx claude-agent-teams add claude-md/fullstack ./app # CLAUDE.md for fullstack
npx claude-agent-teams add spawn-prompts/architect # role template
Check your project is configured correctly — feature flag, CLAUDE.md, unfilled placeholders, file ownership rules, tmux.
`bash`
npx claude-agent-teams validate
npx claude-agent-teams validate ./my-project
Every command supports --help:
`bash`
npx claude-agent-teams init --help
npx claude-agent-teams list --help
npx claude-agent-teams add --help
npx claude-agent-teams info --help
`bash`
npx claude-agent-teams init # 1. set up your project
npx claude-agent-teams list prompts # 2. find a team prompt
npx claude-agent-teams info prompts/code-review # 3. preview it
npx claude-agent-teams add prompts/code-review # 4. grab it
vim CLAUDE.md # 5. fill in {{ placeholders }}
claude # 6. start Claude Code, paste the prompt
Copy-paste these into Claude Code to spin up a team. Each one defines roles, tasks, and file ownership.
| Template | Use case |
|:---|:---|
| Quickstart | Your first team — minimal, 2 teammates, learn the basics |
| Code Review | Parallel PR review — security, performance, test lenses |
| Debugging | Competing hypotheses — multiple theories in parallel |
| Feature Development | Parallel module building with plan approval |
| Refactoring | Parallel module refactoring — shared interface, independent internals |
| Research & Exploration | Multi-angle design exploration — breadth before depth |
| Cross-Layer | Frontend + backend + DB + tests — one teammate per layer |
| Migration | Framework/language migration — each module independently |
| Test Suite | Parallel test writing — one teammate per module |
| Documentation | Parallel docs — API ref, user guide, contributor guide |
Every teammate auto-reads CLAUDE.md from your project root. This is where file ownership, code standards, and team conventions live. init installs one for you.
| Template | For |
|:---|:---|
| Base | Any project |
| Monorepo | Multi-package workspaces (Nx, Yarn Workspaces, Lerna) |
| Fullstack | Frontend / backend / database layers |
Teammates don't inherit conversation history. These give each role full context from the start — paste them when spawning a teammate.
| Role | Responsibility |
|:---|:---|
| Architect | Design systems, define interfaces, review plans |
| Implementer | Build code — frontend, backend, or fullstack |
| Tester | Write tests, validate coverage, find edge cases |
| Reviewer | Review through a lens — security, performance, a11y |
| Researcher | Investigate options, evaluate tradeoffs |
| Devil's Advocate | Challenge assumptions, find failure modes |
5–6 tasks per teammate is the sweet spot.
| Template | Work type |
|:---|:---|
| Feature | New feature with dependency chains across 3-4 teammates |
| Refactor | Foundation → modules → verification sequence |
| Investigation | Hypothesis-driven debugging with parallel investigation |
How teammates hand off work and stay in sync.
| Pattern | Flow |
|:---|:---|
| Contract-First | Define interfaces → approve → implement in parallel → verify |
| Pipeline | Sequential stages with parallel work within each |
| Peer Review | Implement in parallel → cross-review → fix → merge |
Decision frameworks, lifecycle management, and common pitfalls.
| Guide | Covers |
|:---|:---|
| When to Use Teams | Single session vs. subagents vs. agent teams — decision flowchart |
| Team Lifecycle | Create → monitor → steer → shutdown → cleanup |
| Sizing & Cost | Team size, model selection, token budgets |
| Anti-Patterns | 10 common mistakes and how to fix them |
| Troubleshooting | Teammates not appearing, stale tasks, orphaned sessions |
| File | Covers |
|:---|:---|
| Settings | Feature flag, display modes, tmux/iTerm2 setup |
| Permissions | Permission presets for dev, prod, and read-only teams |
| Action | Key |
|:---|:---|
| Select teammate | Shift+Up/Down |Ctrl+T
| Toggle task list | |Shift+Tab
| Delegate mode | |Enter
| View teammate session | |Escape
| Exit teammate view | |
No two teammates should edit the same file. Set file ownership in your CLAUDE.md and spawn prompts. Everything else is flexible — this isn't.
`bash``
npm test
50 tests covering all commands, flags, template integrity, and package structure. Zero dependencies.
See CONTRIBUTING.md.