Skill

claude-code:agent-team

Orchestrates Claude Code agent teams: spawn teammates, assign tasks with dependencies, manage communication via messages or broadcasts, configure modes, and set quality gate hooks.

developer-tools

Install

npx claudepluginhub bendrucker/claude --plugin claude-code

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGlobGrepBashWebFetch(domain:code.claude.com)

Preview

Describe the task and team structure in natural language. Claude creates the team, spawns teammates, and coordinates work.

Supporting Assets

references/hooks.mdreferences/interaction.mdreferences/practices.md

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Parent Repo Stars10

Parent Repo Forks1

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Agent Teams

Team Lifecycle

Describe the task and team structure in natural language. Claude creates the team, spawns teammates, and coordinates work.

Delegate mode (Shift+Tab): restricts the lead to coordination-only tools — no direct implementation
Plan approval: require teammates to plan before implementing. The teammate works read-only until the lead approves.
Shutdown: ask the lead to shut down teammates individually, then clean up the team. Always clean up via the lead.

Task Management

Tasks: pending, in progress, completed. Tasks can depend on other tasks — blocked tasks unlock automatically when dependencies complete.

Lead assigns: tell the lead which task to assign
Self-claim: teammates pick up unassigned, unblocked tasks after finishing
File locking prevents race conditions on simultaneous claims

Communication

message: send to one specific teammate
broadcast: send to all teammates (use sparingly — costs scale with team size)
Messages deliver automatically; the lead doesn't need to poll
Idle notifications are automatic when a teammate finishes a turn

Architecture

Teams are stored locally:

Team config: ~/.claude/teams/{team-name}/config.json
Task list: ~/.claude/tasks/{team-name}/

The config contains a members array with each teammate's name, agent ID, and type. Teammates read this file to discover each other.

Teammates inherit the lead's permission settings at spawn. Each teammate loads project context (CLAUDE.md, MCP servers, skills) plus the spawn prompt — the lead's conversation history does not carry over.

Limitations

No session resumption for in-process teammates (/resume won't restore them)
Task status can lag — check and nudge if stuck
One team per session, no nested teams
Lead is fixed for the team's lifetime

Known Issues

tmux backend: teammates spawned in tmux panes may never receive their initial prompt or poll their inbox, causing them to idle indefinitely (#23415). A separate race condition between pane creation and shell initialization can prevent the claude command from executing at all (#25315). Use in-process backend (the default) as a workaround.

References

references/hooks.md — TeammateIdle and TaskCompleted quality gate hooks
references/practices.md — task sizing, spawn prompts, file conflicts, team structures
references/interaction.md — display modes, keyboard shortcuts, direct teammate interaction
Agent Teams Documentation