Team Composition Patterns
Skill Verified ActiveDesign 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.
Design optimal agent team compositions by providing sizing heuristics, preset configurations, and agent type selection guidance.
Features
- Agent team sizing heuristics
- Preset team compositions (Review, Debug, Feature, etc.)
- Agent type selection guidance
- Display mode configuration options
Use Cases
- Deciding how many agents to spawn for a task
- Choosing between different team structures (review, feature, debug)
- Selecting the correct subagent_type for specific roles
- Configuring display modes for different environments
Non-Goals
- Performing the actual agent spawning or task execution
- Providing runtime environment setup beyond display mode configuration
- Defining specific task content for each agent
Workflow
- Determine team size based on task complexity.
- Select a suitable preset team composition or define a custom one.
- Choose the appropriate `subagent_type` for each agent role.
- Configure the display mode (tmux, iTerm2, in-process).
Practices
- Team composition strategy
- Agent role definition
- Workflow optimization
Prerequisites
- Claude Code Agent Teams feature enabled
Practical Utility
- info:Usage examplesWhile the skill provides comprehensive guidance, explicit, ready-to-run invocation examples are missing. The documentation describes usage scenarios but not concrete command-line examples.
Installation
First, add the marketplace
/plugin marketplace add wshobson/agents/plugin install agent-teams@claude-code-workflowsQuality Score
VerifiedTrust Signals
Similar Extensions
Review Pull Request
100Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Claude Handoff
100Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
Unslop Review
100Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment", "make this feedback sound human", "review this PR", "code review", "/review", "/unslop-review". Auto-triggers when reviewing PRs.
Codex PR Review
100Revisa pull requests en proyectos Drupal 11 (u otro) siguiendo la metodología Codex (lógica de negocio, edge cases de hooks/queries, seguridad, performance, completitud). Genera un informe .md en la carpeta del IDE detectado (.antigravity/, .cursor/, .vscode/ o docs/) con hallazgos por severidad y soluciones accionables. Usar cuando el usuario pida "revisión Codex", "revisión de PR", "revisar PR", "revisar PR