Assemble a multi-agent team and implement the functionality described in $ARGUMENTS.
Usage:
/team <task description>— Spawn a full team and implement the described functionality
Instructions:
- Read the task description from
$ARGUMENTS.
- If $ARGUMENTS is empty, ask the user to describe the functionality to implement before continuing.
- Assess the task to determine team composition:
- Does the task involve any UI or user-facing interface? → include 1–2 designers - How complex is the implementation? → 1 developer for simple tasks, up to 3 for complex ones - Always include at least 1 tester
- Create the team using
TeamCreatewith a short kebab-case name derived from the task (e.g.user-auth,dashboard-filters). - Create a task list using
TaskCreateto track deliverables for each role before spawning agents:
- One task for the product owner: "Write requirements and acceptance criteria" - One task per designer (if applicable): "Design UI/UX for " - One task per developer: "Implement " - One task per tester: "Write tests for "
- Spawn the Product Owner using the Task tool (
subagent_type: general-purpose):
- Provide the full task description from $ARGUMENTS and the team name - Their job: - Write detailed requirements and acceptance criteria for the feature - Check for a project lore file (LORE.md, docs/lore.md, .agent/lore.md, or similar) and update it with any relevant context about the project decisions or domain knowledge this feature introduces - Mark their task as completed via TaskUpdate - Message the team lead when done
- Wait for the Product Owner to finish before continuing.
- If the task involves any UI, spawn 1–2 Designers (
subagent_type: general-purpose) in parallel:
- Provide the team name and the PO's requirements - Their job: - Design the UI/UX: component structure, layout, interactions, and any visual decisions - Document design decisions in a design note or inline comments - Mark their task as completed via TaskUpdate - Message the team lead when done - Wait for all designers to finish before starting development.
- Spawn 1–3 Developers (
subagent_type: general-purpose) based on complexity:
- Provide the team name, PO requirements, and design notes (if any) - If multiple developers are spawned, divide the work clearly (e.g. by layer: frontend/backend, or by feature area) - Their job: - Implement the functionality according to requirements and designs - Mark their task as completed via TaskUpdate - Message the team lead when done - Wait for all developers to finish before starting testing.
- Spawn 1–2 Testers (
subagent_type: general-purpose):
- Provide the team name, PO requirements, and a summary of what was implemented - Their job: - Test the implemented functionality manually and/or via automated tests - Write or update e2e tests and/or unit tests to cover the new behaviour - Report any bugs or regressions found to the team lead - Mark their task as completed via TaskUpdate - Message the team lead when done
- Collect results and present a final summary to the user covering:
- What was implemented - Design decisions made (if any) - Tests added or updated - Any issues, bugs, or recommended follow-ups
- Shut down the team gracefully:
- Send a shutdown_request to each teammate via SendMessage - Once all have confirmed, call TeamDelete