Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding team size, selecting agent types, or configuring team presets for multi-agent workflows.
From agent-teamsnpx claudepluginhub jadecli/jadecli-claude-plugins --plugin agent-teamsThis skill uses the workspace's default tool permissions.
references/agent-type-selection.mdreferences/preset-teams.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides slash command development for Claude Code: structure, YAML frontmatter, dynamic arguments, bash execution, user interactions, organization, and best practices.
Best practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.
| Complexity | Team Size | When to Use |
|---|---|---|
| Simple | 1-2 | Single-dimension review, isolated bug, small feature |
| Moderate | 2-3 | Multi-file changes, 2-3 concerns, medium features |
| Complex | 3-4 | Cross-cutting concerns, large features, deep debugging |
| Very Complex | 4-5 | Full-stack features, comprehensive reviews, systemic issues |
Rule of thumb: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.
team-reviewerteam-debuggerteam-lead + 2x team-implementerteam-lead + 1x frontend team-implementer + 1x backend team-implementer + 1x test team-implementergeneral-purposeteam-reviewerteam-lead + 2x team-implementer + 1x team-reviewerWhen spawning teammates with the Task tool, choose subagent_type based on what tools the teammate needs:
| Agent Type | Tools Available | Use For |
|---|---|---|
general-purpose | All tools (Read, Write, Edit, Bash, etc.) | Implementation, debugging, any task requiring file changes |
Explore | Read-only tools (Read, Grep, Glob) | Research, code exploration, analysis |
Plan | Read-only tools | Architecture planning, task decomposition |
agent-teams:team-reviewer | All tools | Code review with structured findings |
agent-teams:team-debugger | All tools | Hypothesis-driven investigation |
agent-teams:team-implementer | All tools | Building features within file ownership boundaries |
agent-teams:team-lead | All tools | Team orchestration and coordination |
Key distinction: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.
Configure in ~/.claude/settings.json:
{
"teammateMode": "tmux"
}
| Mode | Behavior | Best For |
|---|---|---|
"tmux" | Each teammate in a tmux pane | Development workflows, monitoring multiple agents |
"iterm2" | Each teammate in an iTerm2 tab | macOS users who prefer iTerm2 |
"in-process" | All teammates in same process | Simple tasks, CI/CD environments |
When building custom teams:
team-lead or have the user coordinate directly