Agent Teams

This turns Claude Code into a multi-session team where each teammate is a full Claude instance with its own context window, not just a subagent reporting back. You get a lead that delegates tasks and 2-4 teammates working on non-overlapping files simultaneously, coordinating through shared task lists and file locks. The sweet spot is 3-5 teammates on cross-layer work like building an API endpoint plus UI plus tests in parallel. Beyond five teammates, you spend more time coordinating than you save. The plan approval flow before implementation prevents wasted work, and delegate mode keeps the lead focused on coordination instead of coding. Use worktrees instead if you want to compare competing approaches, or subagents for quick throwaway exploration.

skills.sh installs: 161
GitHub stars: 2.9K
last updated: Jun 8, 2026

View on GitHub

Install

$ npx -y skills add rohitg00/pro-workflow --skill agent-teams --agent claude-code

Installs into .claude/skills of the current project.

Files

Agent Teams

Coordinate multiple Claude Code sessions working on the same codebase simultaneously.

Enable

export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
claude  # starts as team lead

The first session becomes the team lead. Subsequent sessions in the same repo join as teammates.

Architecture

Team Lead (coordinates, delegates, reviews)
  ├── Teammate 1 (owns task A, messages lead + peers)
  ├── Teammate 2 (owns task B, messages lead + peers)
  └── Teammate 3 (owns task C, messages lead + peers)
      │
      └── Shared: task list + mailbox + file locks

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.