From cc-godmode
Orchestrates experimental Agent Teams to run parallel CC_GodMode agents as teammates coordinated via SharedTaskList for large features with independent modules. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
npx claudepluginhub cubetribe/claudecode_godmode-onThis skill uses the workspace's default tool permissions.
> **Status:** Experimental — requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`
Orchestrates Claude Code agent teams for parallel multi-agent workflows on complex tasks using TeamCreate, SendMessage, TaskUpdate, and shared task lists. Enable with --enable-teams flag.
Coordinates multiple Claude Code instances as agent teams for workflows needing inter-agent communication. Covers TeamCreate, SendMessage types, task coordination, hooks, and orchestration patterns.
Orchestrates Claude Code agent teams: spawn teammates, assign tasks with dependencies, manage communication via messages or broadcasts, configure modes, and set quality gate hooks.
Share bugs, ideas, or general feedback.
Status: Experimental — requires
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1When to use: Large features where multiple agents can work truly in parallel
Agent Teams allow multiple Claude Code instances to coordinate through a SharedTaskList. Instead of the Orchestrator calling agents sequentially via Task tool, teammates work independently and pick up tasks from a shared queue.
Add to your environment or settings.json:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
| Teammate | Role | Model | Isolation |
|---|---|---|---|
| Architect | Design & planning | opus | — |
| Builder | Implementation | sonnet | worktree |
| Validator | Code quality | sonnet | worktree |
| Tester | UX quality | sonnet | worktree |
| Scribe | Documentation | haiku | — |
Recommended team size: 3–5 teammates for optimal coordination.
Tasks follow this lifecycle:
pending → in_progress → completed
→ failed
blockedBy arrays{
"tasks": [
{"id": "1", "name": "Design auth module", "assignee": "architect", "status": "completed"},
{"id": "2", "name": "Implement auth API", "assignee": "builder", "blockedBy": ["1"], "status": "in_progress"},
{"id": "3", "name": "Implement auth UI", "assignee": "builder", "blockedBy": ["1"], "status": "in_progress"},
{"id": "4", "name": "Validate auth code", "assignee": "validator", "blockedBy": ["2", "3"], "status": "pending"},
{"id": "5", "name": "Test auth UX", "assignee": "tester", "blockedBy": ["2", "3"], "status": "pending"}
]
}
| Hook | Purpose | Exit Code 2 |
|---|---|---|
TeammateIdle | Fires when teammate about to go idle | Teammate continues working |
TaskCompleted | Fires when task marked complete | Prevents completion, sends feedback |
| Scenario | Use Agent Teams? |
|---|---|
| Large feature with independent modules | YES |
| Multiple parallel investigations | YES |
| Small bug fix | NO — overhead not worth it |
| API change (strict sequence required) | NO — sequential workflow needed |
| Research task | NO — single agent sufficient |
blockedBy