Help us improve
Share bugs, ideas, or general feedback.
From playbooks-virtuoso
Spawns and coordinates a pre-composed agent team from a team definition file, resolving agents and skills and running the workflow. Useful for dispatching development teams or multi-phase task coordination.
npx claudepluginhub krzysztofsurdy/code-virtuoso --plugin agents-virtuosoHow this skill is triggered — by the user, by Claude, or both
Slash command
/playbooks-virtuoso:dispatching-agent-teams <team-name><team-name>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read a team definition file, resolve its agents and skills, and execute the coordination protocol. The team file is the recipe - this skill is the cook.
Creates agent-almanac team composition files defining purpose, members, coordination patterns, task decomposition, and registry integration. Use for multi-agent workflows, complex reviews, or recurring collaborations.
Catalogs pre-composed agent teams (development-team, review-squad, war-room) with purpose, roster, workflow, and selection guidance. Use when browsing or choosing a team to dispatch.
Sets up multi-agent teams for complex projects with file-based planning, per-agent directories, and teammate spawning. Triggers on team/swarm/start-project requests.
Share bugs, ideas, or general feedback.
Read a team definition file, resolve its agents and skills, and execute the coordination protocol. The team file is the recipe - this skill is the cook.
| Principle | Meaning |
|---|---|
| Team file is the contract | Follow the workflow, entry/exit criteria, and coordination rules defined in the team file. Do not improvise the process. |
| Detect capabilities first | Check what spawning mode the platform supports before dispatching. Peer mode if available, sequential fallback otherwise. |
| Skills before agents | Preload the team's bundled skills before spawning any agent. Agents need their reference material from the start. |
| Respect coordination rules | If the team file says "Architect must approve before implementation starts", enforce it. Do not skip gates. |
| Fail early, not late | If a required agent is not installed, stop before dispatching. Do not discover missing agents mid-workflow. |
Teams are discovered from two locations in this order:
teams/{name}.md at the user's project root (user-authored teams)agent-teams skill at skills/tools/agent-teams/teams/{name}.md (or wherever the agent-teams skill is installed)Resolution:
name, lead, agents, skills, workflow.agents list exists as an installed agent definition.skills list exists as an installed skill.The agent-teams skill catalogs the available pre-composed teams (development-team, review-squad, war-room) with their purpose and use cases. To browse what is available before dispatching, consult that skill first.
To author your own team, see spec/team-spec.md and place the file at the project root's teams/{name}.md.
Load the skills listed in the team's skills frontmatter. These provide reference material that agents will need during their work (e.g., testing patterns, API design principles, verification checklists).
Check what the current platform supports:
| Capability | Detection | Mode |
|---|---|---|
| Platform supports agent teams with peer messaging and shared task lists | Team creation tools are available | Peer mode |
| Platform supports sub-agent spawning but no peer messaging | Agent delegation tools are available | Sequential mode |
| Neither | No delegation support | Inline mode - lead executes all phases in the current session |
Then check the team's workflow type for special handling:
| Workflow | Special protocol |
|---|---|
parallel | Check Coordination Rules for per-agent context restrictions. If present, build differential briefs per agent (see spawning-protocol). |
war-room | Use multi-pass rounds: position round, then challenge round, then synthesis. Agents respond with perspective only - no tool use during the debate (see spawning-protocol). |
sequential, hybrid | Standard protocol. |
| Failure | Action |
|---|---|
| Agent not installed | Stop before dispatching. List missing agents with install instructions. |
| Skill not installed | Stop before dispatching. List missing skills with install instructions. |
| Entry criterion not met | Ask user to confirm or waive. Do not silently skip. |
| Phase produces no output | Retry the phase once. If it fails again, report to the lead/user. |
| Gate condition not met | Block the next phase. Report what failed the gate and what needs to change. |
| Agent times out or errors | Report the error. Ask user whether to retry, skip, or abort the team. |
Before claiming the team run is complete:
Platform-specific tool names and conventions for executing this skill. The instructions above stay portable; the table below maps abstract capabilities to concrete tools per platform.
| Platform | Convention |
|---|---|
| Claude Code | Always create the team with the TeamCreate tool before dispatching any work. Never spawn multiple Agent tool calls directly when a team workflow is available. After TeamCreate, dispatch tasks through the team. |
| Cursor | (TBD) Use the platform's multi-agent coordination feature if available; otherwise fall back to sequential sub-agent dispatch. |
| Windsurf | (TBD) Use the platform's multi-agent coordination feature if available; otherwise fall back to sequential sub-agent dispatch. |
| Other | Use the platform's equivalent for instantiating a multi-agent team with a shared task list. If no such mechanism exists, run in sequential mode. |
| Reference | Contents |
|---|---|
| spawning-protocol | Detailed spawning steps for peer, sequential, and inline modes |
| Situation | Recommended Skill |
|---|---|
| Need to discover which teams are available | using-ecosystem |
| Need to create a new team definition | Use template/team-template.md and spec/team-spec.md |
| Need to dispatch agents without a team file | dispatching-parallel-agents or subagent-driven-development |
| Need to verify work before closing a phase | verification-before-completion |