agent-teams

Name: agent-teams
Author: krzysztofsurdy

6installs1forks

How to install agent-teams?

krzysztofsurdy/code-virtuoso/agent-teams

$npx -y skills add krzysztofsurdy/code-virtuoso --skill agent-teams

Installs into the current project.

Summary

Pre-composed agent team library. Use when the user asks which teams are available, what a team does, when to pick one team over another, or to browse multi-agent compositions. Catalogs ready-to-run teams (development team, review squad, war room) with their purpose, agent roster,

Files · 1

View on GitHub

SKILL.md

1	# Agent Teams Library
2
3	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.
4
5	## Available Teams
6
7	\| Team \| Workflow \| Lead \| Use when \|
8	\|---\|---\|---\|---\|
9	\| [development-team](teams/development-team.md) \| hybrid \| Product Manager \| Delivering a full feature from requirements to merged PR \|
10	\| [review-squad](teams/review-squad.md) \| parallel \| Reviewer \| Multi-perspective code review before merging significant changes \|
11	\| [war-room](teams/war-room.md) \| war-room \| Architect \| Structured technical debate that ends in a decision (architecture choice, tech selection, design trade-off) \|
12
13	## How to Pick a Team
14
15	\| Situation \| Recommended Team \|
16	\|---\|---\|
17	\| "I need to ship feature X end-to-end" \| development-team \|
18	\| "Code review this PR thoroughly" \| review-squad \|
19	\| "We need to decide between X and Y" \| war-room \|
20	\| "Just review the diff" \| Skip the team, delegate to `reviewer` agent directly \|
21	\| "Investigate this area" \| Skip the team, delegate to `investigator` agent directly \|
22
23	If no team fits the work, skip the team and chain individual agents (see the `using-ecosystem` skill's chaining patterns).
24
25	## Team File Format
26
27	Every team file follows the team specification (`spec/team-spec.md`):
28
29	- Frontmatter: `name`, `description`, `lead`, `agents`, `skills`, `workflow`
30	- Body: Purpose, Workflow, Entry/Exit Criteria, Coordination Rules, Spawning
31
32	The dispatcher reads these fields to resolve the team, verify entry criteria, and execute the workflow in the appropriate spawning mode.
33
34	## Authoring Your Own Team
35
36	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.
37
38	See `spec/team-spec.md` for the full team format and `template/team-template.md` for a starter.
39
40	## Integration with Other Skills
41
42	\| Situation \| Recommended Skill \|
43	\|---\|---\|
44	\| Run a team you picked from this catalog \| `dispatching-agent-teams` \|
45	\| Discover what agents and skills are available \| `using-ecosystem` \|
46	\| Decide between teams and ad-hoc agent chaining \| `using-ecosystem` \|
47	\| Author a new team definition \| `spec/team-spec.md` and `template/team-template.md` \|

People who liked this also viewed

6 picks

Type

agent-teams

6installs1forks

View on GitHub

How to install agent-teams?

krzysztofsurdy/code-virtuoso/agent-teams

$npx -y skills add krzysztofsurdy/code-virtuoso --skill agent-teams

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Agent Teams Library
2
3	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.
4
5	## Available Teams
6
7	\| Team \| Workflow \| Lead \| Use when \|
8	\|---\|---\|---\|---\|
9	\| [development-team](teams/development-team.md) \| hybrid \| Product Manager \| Delivering a full feature from requirements to merged PR \|
10	\| [review-squad](teams/review-squad.md) \| parallel \| Reviewer \| Multi-perspective code review before merging significant changes \|
11	\| [war-room](teams/war-room.md) \| war-room \| Architect \| Structured technical debate that ends in a decision (architecture choice, tech selection, design trade-off) \|
12
13	## How to Pick a Team
14
15	\| Situation \| Recommended Team \|
16	\|---\|---\|
17	\| "I need to ship feature X end-to-end" \| development-team \|
18	\| "Code review this PR thoroughly" \| review-squad \|
19	\| "We need to decide between X and Y" \| war-room \|
20	\| "Just review the diff" \| Skip the team, delegate to `reviewer` agent directly \|
21	\| "Investigate this area" \| Skip the team, delegate to `investigator` agent directly \|
22
23	If no team fits the work, skip the team and chain individual agents (see the `using-ecosystem` skill's chaining patterns).
24
25	## Team File Format
26
27	Every team file follows the team specification (`spec/team-spec.md`):
28
29	- Frontmatter: `name`, `description`, `lead`, `agents`, `skills`, `workflow`
30	- Body: Purpose, Workflow, Entry/Exit Criteria, Coordination Rules, Spawning
31
32	The dispatcher reads these fields to resolve the team, verify entry criteria, and execute the workflow in the appropriate spawning mode.
33
34	## Authoring Your Own Team
35
36	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.
37
38	See `spec/team-spec.md` for the full team format and `template/team-template.md` for a starter.
39
40	## Integration with Other Skills
41
42	\| Situation \| Recommended Skill \|
43	\|---\|---\|
44	\| Run a team you picked from this catalog \| `dispatching-agent-teams` \|
45	\| Discover what agents and skills are available \| `using-ecosystem` \|
46	\| Decide between teams and ad-hoc agent chaining \| `using-ecosystem` \|
47	\| Author a new team definition \| `spec/team-spec.md` and `template/team-template.md` \|

People who liked this also viewed

6 picks

Type