Agent skill · product strategy · wshobson
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.
Why this skill is useful
Provides specific team composition patterns and heuristics for optimizing agent workflows that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-05. 38,570 stars on the source repository.
What this skill does
Team Composition Patterns Best practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature. When to Use This Skill Deciding how many teammates to spawn for a task Choosing between preset team configurations Selecting the right agent type (subagenttype) for each role Configuring teammate display modes (tmux, iTerm2, in-process) Building custom team compositions for non-standard workflows Team Sizing Heuristics 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. Preset Team Compositions Review Team Size: 3 reviewers Agents: 3x team-reviewer Default dimensions: security, performance, architecture Use when: Code changes need multi-dimensional quality assessment Debug Team Size: 3 investigators Agents: 3x team-debugger Default hypotheses: 3 competing hypotheses Use when: Bug has multiple plausible root causes Feature Team Size: 3 (1 lead + 2 implementers) Agents: 1x team-lead + 2x team-implementer Use when: Feature can be decomposed into parallel work streams Fullstack Team Size: 4 (1 lead + 3 implementers) Agents: 1x team-lead + 1x frontend team-implementer + 1x backend team-implementer + 1x test team-implementer Use when: Feature spans frontend, backend, and test layers Research Team Size: 3 researchers Agents: 3x general-purpose Default areas: Each assigned a different research question, module, or topic Capabilities: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch) Use when: Need to understand a c …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wshobson/team-composition-patterns