Agent skill
teams
Agent Teams orchestration for multi-instance parallel work. Use when: - User mentions "use teams", "parallel agents", "split work", "fan out" - Task has 3+ independent workstreams - Large-scale refactoring across unrelated files - User says "divide and conquer", "multi-instance"
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/teams
SKILL.md
Agent Teams Orchestration
Delegates to the Maestro agent for coordinating multiple independent Claude Code instances.
When to Use Teams
| Scenario | Teams? | Why |
|---|---|---|
| 3+ independent file areas | Yes | Maximum parallelism |
| Frontend + Backend + Tests | Yes | No file conflicts |
| Sequential dependent work | No | Use subagents instead |
| Quick single investigation | No | Overhead not worth it |
| Large codebase analysis | Yes | Independent context per agent |
| Competing approaches | Yes | Explore in parallel |
Prerequisites
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS: "1"must be set (enabled by default in cc-settings)- For split panes: tmux or iTerm2 recommended
Output
Report: team composition, task assignments, coordination strategy, and progress.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?