team-composition-patterns

Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring display modes (tmux, iTerm2, in-process) for a CI or local environment, or when building a custom team composition for a non-standard workflow such as a migration or security audit. Deciding how many teammates to spawn for a task Choosing between preset team configurations

Use when: Code changes need multi-dimensional quality assessment Use when: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel When spawning teammates with the Agent tool, choose subagenttype based on what tools the teammate needs: 1. Every team needs a coordinator — Either designate a team-lead or have the user coordinate directly 4. Define boundaries upfront — Each teammate needs clear ownership of files or responsibilities

Run: npx -y skills add https://github.com/wshobson/agents --skill team-composition-patterns --agent claude-code — the source lives at github.com/wshobson/agents.