teams.do
You are an expert in teams.do — group agents into functional teams for higher-level coordination.
When to Use
Activate when the user wants to coordinate multiple agents as a team rather than orchestrating individuals.
Core Usage
import { product, engineering, marketing, sales } from 'teams.do'
// Team-level calls — the team coordinates internally
const mvp = await product`define the MVP for ${idea}`
const app = await engineering`build ${mvp}`
await marketing`launch ${app}`
await sales`start outreach for ${app}`
Team Composition
| Team |
Agents |
Responsibility |
product |
Priya |
Specs, roadmaps, priorities, stakeholder coordination |
engineering |
Ralph, Tom, Quinn |
Build, architecture, testing, code review |
marketing |
Mark |
Copy, content, launches, brand |
sales |
Sally |
Outreach, demos, pipeline, closing |
design |
Rae |
UI, frontend, accessibility, components |
Individual vs Team
import { ralph, tom, quinn } from 'agents.do' // individuals
import { engineering } from 'teams.do' // team
// Individual — direct control
const code = await ralph`implement ${spec}`
const review = await tom`review ${code}`
// Team — let the team coordinate
const shipped = await engineering`implement, review, and test ${spec}`
Use individuals when you need predictable, sequential handoffs. Use teams when you want the group to self-organize.
Custom Teams
import { Startup } from 'startups.do'
import { engineering, product } from 'teams.do'
// Teams are composable
export default Startup({
name: 'MyStartup',
teams: {
core: { ...engineering, ...product },
growth: { ...sales, ...marketing },
}
})
Best Practices
- Prefer team-level calls for strategic work (
product\plan Q2``)
- Use individual agents for precise, sequential workflows
- Teams self-coordinate — don't micromanage the internal handoffs
1---2name: teams-do3description: teams.do — coordinate groups of agents as functional teams (product, engineering, marketing, sales). Team-level imports and cross-team workflow patterns.4---56# teams.do78You are an expert in [teams.do](https://teams.do) — group agents into functional teams for higher-level coordination.910## When to Use1112Activate when the user wants to coordinate multiple agents as a team rather than orchestrating individuals.1314## Core Usage1516```typescript17import { product, engineering, marketing, sales } from 'teams.do'1819// Team-level calls — the team coordinates internally20const mvp = await product`define the MVP for ${idea}`21const app = await engineering`build ${mvp}`22await marketing`launch ${app}`23await sales`start outreach for ${app}`24```2526## Team Composition2728| Team | Agents | Responsibility |29|------|--------|---------------|30| `product` | Priya | Specs, roadmaps, priorities, stakeholder coordination |31| `engineering` | Ralph, Tom, Quinn | Build, architecture, testing, code review |32| `marketing` | Mark | Copy, content, launches, brand |33| `sales` | Sally | Outreach, demos, pipeline, closing |34| `design` | Rae | UI, frontend, accessibility, components |3536## Individual vs Team3738```typescript39import { ralph, tom, quinn } from 'agents.do' // individuals40import { engineering } from 'teams.do' // team4142// Individual — direct control43const code = await ralph`implement ${spec}`44const review = await tom`review ${code}`4546// Team — let the team coordinate47const shipped = await engineering`implement, review, and test ${spec}`48```4950Use individuals when you need predictable, sequential handoffs. Use teams when you want the group to self-organize.5152## Custom Teams5354```typescript55import { Startup } from 'startups.do'56import { engineering, product } from 'teams.do'5758// Teams are composable59export default Startup({60 name: 'MyStartup',61 teams: {62 core: { ...engineering, ...product },63 growth: { ...sales, ...marketing },64 }65})66```6768## Best Practices6970- Prefer team-level calls for strategic work (`product\`plan Q2\``)71- Use individual agents for precise, sequential workflows72- Teams self-coordinate — don't micromanage the internal handoffs