team-composition-patterns

Agent team sizing relies on proven heuristics and preset configurations to match team size with task complexity. You can use ready-to-spawn templates for review, debug, feature, or fullstack teams to quickly assemble an optimally sized group.

Configuring agent roles for a security audit requires selecting the correct subagent_type for each position to ensure agents have the necessary tools. Custom team composition guidance helps map specific roles tailored for complex, non-standard workflows like migrations and audits.

Display mode configuration supports tmux, iTerm2, and in-process modes for both local development and CI environments. Guidance is provided to help you select the correct display mode based on whether your agents are running locally or in an automated pipeline.

Preset configurations include a ready-to-spawn 3-person review team template. You can spawn this preset directly and then tailor individual role assignments and display modes to fit your specific code review requirements.

Choosing between a feature team and a debug team depends on your workflow goals: feature teams drive new development, while debug teams focus on resolving existing issues. Sizing heuristics and preset configurations differentiate the role selection and team structure for each scenario.

Subagent_type mapping assigns specific tool access to each agent role within your team. For complex workflows like migrations, custom team composition guidance helps you select the correct subagent_type so every agent has the appropriate tools available.