Team

Team Composition Examples

Phase 1: Team Creation

TeamCreate(
  team_name: "{topic}-team",
  description: "{task description}"
)

Phase 2: Task Creation + Member Deployment

Create tasks first

Define each member's work clearly with TaskCreate. Members claim and work on their tasks.

Member prompts — this is the most important part

Each member's prompt must include:

# Team: {team name}
# Your role: {specific role and perspective}
# Your task: {what to do}

## Context
{2-3 lines on what the project is}
{What is currently being worked on and why this team was launched}
{What roles the other team members have}

## What you must deliver
{Specific deliverables}

## Rules
- Read actual code/data and provide evidence. No guessing.
- If you disagree with other team members, rebut with evidence. Do not just agree.
- If uncertain, explicitly state that you are uncertain.

Do not throw it over assuming "they'll get it." Team members have no knowledge of our conversation.

Deployment

Agent(
  team_name: "{team name}",
  name: "{role name}",
  prompt: "{prompt above}",
  run_in_background: true
)

Send all independent members simultaneously.

Phase 3: Coordination + Discussion

The core of Teams. The decisive difference from subagents.

1. Share member results. Use SendMessage to relay member A's findings to member B.
2. Encourage disagreement. If all members agree, be suspicious instead. Deliberately request counterarguments.
3. Converge through discussion. Compare evidence from both sides and have members judge which is stronger.
4. Set direction as the leader. If the discussion does not converge, make the judgment yourself. Or escalate to the user.

Phase 4: Summary Report

## Team Results: {task description}

### Team Composition
| Member | Role | Perspective |
|--------|------|-------------|
| {name} | {role} | {what perspective they examined from} |

### Key Findings
1. {Most important finding}
2. {Second}

### Discussion Summary (if applicable)
- {Issue}: {Member A} argues {claim} (evidence: ...), {Member B} argues {claim} (evidence: ...)
- **Conclusion:** {How it converged, or whether it remains unresolved}

### Recommended Next Actions
1. {Specific action}

### Confidence: HIGH / MEDIUM / LOW

Phase 5: Cleanup

TeamDelete()

Always clean up when the team is done. Do not leave orphan teams.

When to Use Teams vs Subagents

Status Report

• DONE — Team completed, summary report written, team cleaned up.
• DONE_WITH_CONCERNS — Completed but unresolved issues exist. Specified.
• BLOCKED — Multiple members failed. State reason.
• NEEDS_CONTEXT — Insufficient information. Specify what is needed.