Topics
- agent-teams
- multi-agent
- team-composition
- team-sizing
- agent-types
- coordination
- claude-code
- workflow-design
What it does
Guides selecting agent team sizes, preset configurations (review, debug, feature, fullstack, research, security, migration), and agent types (general-purpose, Explore, Plan, team-reviewer, team-debugger, team-implementer, team-lead) based on task complexity and required capabilities. Use this skill when deciding how many agents to spawn, choosing between team templates, or matching agent types to their available tools.
Generated from the current SKILL.md.
Frequently asked
What agent types should I use for code review versus implementation?
Use `team-reviewer` for code review (read/search/Bash plus structured task tools), and `team-implementer` for building features (read/write/edit plus task coordination). Never use read-only agents like `Explore` or `Plan` for implementation tasks.
How many agents should I spawn for a feature that spans frontend, backend, and tests?
Use a Fullstack Team: 1x `team-lead` + 1x frontend `team-implementer` + 1x backend `team-implementer` + 1x test `team-implementer`. This composition lets you parallelize work across three implementation layers with a lead coordinating.
What display mode should I use in CI/CD environments?
Use `in-process` mode, configured in `~/.claude/settings.json`. This runs all teammates in the same process without requiring tmux or iTerm2 and works reliably in automated environments.
Can I have two agents working on the same review dimension?
No. Two reviewers with overlapping focus areas waste tokens and produce duplicate findings. Define distinct dimensions for each reviewer, such as security, performance, and architecture.
What tools are available to a `team-lead`?
A `team-lead` has read/search/Bash plus Agent Teams coordination tools for spawning teammates and orchestrating work. They cannot write files directly — implementers handle that.
Generated from the current SKILL.md. These answers refresh after source changes.