Stats
Actions
Tags
From playbooks-virtuoso
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/playbooks-virtuoso:agent-teams [optional: team name to describe][optional: team name to describe]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A catalog of pre-composed agent teams. Each team bundles a roster of agents, a coordination workflow, and entry/exit criteria into a ready-to-use unit. Pick a team and dispatch it via the `dispatching-agent-teams` skill.
A catalog of pre-composed agent teams. Each team bundles a roster of agents, a coordination workflow, and entry/exit criteria into a ready-to-use unit. Pick a team and dispatch it via the dispatching-agent-teams skill.
| Team | Workflow | Lead | Use when |
|---|---|---|---|
| development-team | hybrid | Product Manager | Delivering a full feature from requirements to merged PR |
| review-squad | parallel | Reviewer | Multi-perspective code review before merging significant changes |
| war-room | war-room | Architect | Structured technical debate that ends in a decision (architecture choice, tech selection, design trade-off) |
| Situation | Recommended Team |
|---|---|
| "I need to ship feature X end-to-end" | development-team |
| "Code review this PR thoroughly" | review-squad |
| "We need to decide between X and Y" | war-room |
| "Just review the diff" | Skip the team, delegate to reviewer agent directly |
| "Investigate this area" | Skip the team, delegate to investigator agent directly |
If no team fits the work, skip the team and chain individual agents (see the using-ecosystem skill's chaining patterns).
Every team file follows the team specification (spec/team-spec.md):
name, description, lead, agents, skills, workflowThe dispatcher reads these fields to resolve the team, verify entry criteria, and execute the workflow in the appropriate spawning mode.
User-authored teams live at the project root in teams/{name}.md. The dispatcher discovers project teams before falling back to the bundled library here, so project teams can override bundled ones by name.
See spec/team-spec.md for the full team format and template/team-template.md for a starter.
| Situation | Recommended Skill |
|---|---|
| Run a team you picked from this catalog | dispatching-agent-teams |
| Discover what agents and skills are available | using-ecosystem |
| Decide between teams and ad-hoc agent chaining | using-ecosystem |
| Author a new team definition | spec/team-spec.md and template/team-template.md |
npx claudepluginhub krzysztofsurdy/code-virtuoso --plugin agents-virtuosoSpawns 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.
Creates a multi-agent team composition file with purpose definition, member selection, coordination patterns, and registry integration. Use when formalizing recurring collaborative workflows.
Interactive agent picker for browsing and composing parallel teams on demand. Works with flat or domain-subdirectory agent collections.