$npx -y skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill team-agentsSpin up coordinated agent teams for any task. Reusable framework for TeamCreate/SendMessage/TaskList patterns. Use when user says "team-agents", "spin up a team", "use teammates", "parallel agents", "coordinate agents", "fan out", or wants multiple agents working together with co
| 1 | # /team-agents — Coordinated Agent Teams |
| 2 | |
| 3 | ## Config |
| 4 | |
| 5 | ```json |
| 6 | // ~/.claude/settings.json — required |
| 7 | { "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } } |
| 8 | ``` |
| 9 | |
| 10 | ```json |
| 11 | // ~/.claude.json — display mode (default: "auto") |
| 12 | { "teammateMode": "in-process" } // all in main terminal |
| 13 | { "teammateMode": "tmux" } // split panes (requires tmux/iTerm2) |
| 14 | ``` |
| 15 | |
| 16 | ```bash |
| 17 | claude --teammate-mode in-process # per-session override |
| 18 | ``` |
| 19 | |
| 20 | Requires Claude Code **v2.1.32+**. Without env var, TeamCreate/SendMessage/TaskList tools don't exist — fall back to parallel subagents. |
| 21 | |
| 22 | **In-process keys**: `Shift+Down` cycle teammates, `Enter` view, `Escape` interrupt, `Ctrl+T` toggle tasks. |
| 23 | |
| 24 | ### Quality Gate Hooks |
| 25 | |
| 26 | ```json |
| 27 | // ~/.claude/settings.json |
| 28 | { |
| 29 | "hooks": { |
| 30 | "TeammateIdle": [{ "matcher": "", "hooks": [{ "type": "command", "command": "..." }] }], |
| 31 | "TaskCreated": [{ "matcher": "", "hooks": [{ "type": "command", "command": "..." }] }], |
| 32 | "TaskCompleted": [{ "matcher": "", "hooks": [{ "type": "command", "command": "..." }] }] |
| 33 | } |
| 34 | } |
| 35 | ``` |
| 36 | |
| 37 | Exit code 2 from any hook = reject action + send feedback to agent. |
| 38 | |
| 39 | --- |
| 40 | |
| 41 | ## Usage |
| 42 | |
| 43 | ``` |
| 44 | /team-agents "review this PR for security, perf, and tests" |
| 45 | /team-agents "refactor auth module" --roles 3 |
| 46 | /team-agents "research X" --model haiku |
| 47 | /team-agents "implement feature Y" --plan |
| 48 | /team-agents --manual "build feature Z" |
| 49 | /team-agents --manual "build feature" --worktree |
| 50 | |
| 51 | /team-agents who # presence dots + task state |
| 52 | /team-agents --panes # tmux pane scan |
| 53 | /team-agents zoom scout # toggle zoom on agent's pane |
| 54 | /team-agents sync # git sync all worktrees to main |
| 55 | /team-agents merge scout # merge agent's branch to main |
| 56 | /team-agents compile # gather all reports |
| 57 | /team-agents shutdown # graceful shutdown |
| 58 | /team-agents cleanup # kill idle orphan panes |
| 59 | /team-agents killshot # kill ALL non-lead panes |
| 60 | /team-agents doctor [--fix] # detect ghosts + orphans |
| 61 | ``` |
| 62 | |
| 63 | | Flag | Effect | |
| 64 | |------|--------| |
| 65 | | `--manual` | Human controls agents via lead relay | |
| 66 | | `--worktree` | Each agent gets git worktree + branch | |
| 67 | | `--panes` | Peek at tmux panes | |
| 68 | | `--plan` | Plans are AUTO-APPROVED by leader's inbox poller — generation gate, not human review | |
| 69 | | `--roles N` | Override agent count | |
| 70 | | `--model X` | Override model (sonnet/opus/haiku) | |
| 71 | |
| 72 | --- |
| 73 | |
| 74 | ## When to Use |
| 75 | |
| 76 | | Context | What happens | |
| 77 | |---------|-------------| |
| 78 | | **User types `/team-agents`** | Always Tier 1 (tmux) or Tier 2 (in-process). Never downgrade. | |
| 79 | | **Agent tool without `/team-agents`** | AI spawns subagents directly — no tmux, no TeamCreate. | |
| 80 | | **Cross-Oracle messaging** | Use /talk-to + contacts, not team-agents. | |
| 81 | |
| 82 | **Rule**: `/team-agents` = tmux panes. Plain `Agent()` = quiet subagents. The user's choice of invocation decides the tier. |
| 83 | **Sizing**: 3-5 teammates, 5-6 tasks each. Tokens scale linearly per teammate. |
| 84 | |
| 85 | ### Spawn Fallback Order |
| 86 | |
| 87 | When the user explicitly invokes `/team-agents`, they want tmux panes. **Never downgrade to Tier 3 when Tier 1 or 2 preflight passes** — even for "read-only" or "simple" tasks. The user typed `/team-agents` because they want to SEE agents working. If they wanted quiet subagents, they'd just ask without the skill. |
| 88 | |
| 89 | Try tiers in order. Stop at the first whose preflight passes — **never skip ahead**. |
| 90 | |
| 91 | #### Tier 1 — tmux + team-agents framework (preferred) |
| 92 | |
| 93 | **Preflight** — verify all four before `TeamCreate`: |
| 94 | |
| 95 | ```bash |
| 96 | [ -n "$TMUX" ] || tmux info >/dev/null 2>&1 # 1. inside tmux? |
| 97 | [ "$CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS" = "1" ] # 2. env var set? |
| 98 | # 3. TeamCreate tool loaded? (deferred — ToolSearch select:TeamCreate,TaskCreate,SendMessage,TaskUpdate,TaskList,TeamDelete) |
| 99 | # 4. claude --version >= 2.1.32 |
| 100 | ``` |
| 101 | |
| 102 | All four pass → real team. Teammates spawn into **split tmux panes** with isolated heartbeats, SendMessage each other, get persistent mailboxes, can claim per-agent worktrees. |
| 103 | |
| 104 | #### Tier 2 — in-process team-agents (env + tools, but no tmux) |
| 105 | |
| 106 | env var + tools present but `$TMUX` empty → set `teammateMode: "in-process"` (per-session: `claude --teammate-mode in-process`) and proceed with TeamCreate. All teammates run in the main terminal — cycle with `Shift+Down`, view with `Enter`. Same coordination machinery, less visual separation. |
| 107 | |
| 108 | #### Tier 3 — parallel subagents (Age |