agent-teams
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
Install
With your agent
Install OMGSkills skill "rohitg00/pro-workflow:skills/agent-teams" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/rohitg00/pro-workflow /tmp/pro-workflow && ln -s /tmp/pro-workflow/skills/agent-teams ~/.claude/skills/agent-teamsFrom README
Agent Teams Coordinate multiple Claude Code sessions working on the same codebase simultaneously. Enable The first session becomes the team lead. Subsequent sessions in the same repo join as teammates. Architecture Key difference from subagents: Teammates are full Claude Code sessions. They have their own context window, can use all tools, and message each other directly — not just report back to a parent. Team Sizing | Team Size | Best For | |-----------|----------| | 2 | One builds, one reviews | | 3-5 | Parallel features across layers (API, UI, tests) | | > 5 | Coordination overhead outweighs parallelism | 3-5 teammates is the productive range. Beyond that, the lead spends more time coordinating than the team saves. Task granularity: Aim for 5-6 tasks per teammate. Fewer means underutilization; more means excessive context switching.
More from this repo
context-engineering
Master the four operations of context engineering — Write, Select, Compress, Isolate.
auto-setup
Auto-configure quality gates, hooks, and settings for a new project.
batch-orchestration
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees.