build-with-team

Agent Team Build: $ARGUMENTS

Pre-flight

Before spawning the team:

1. Create or load the plan — There must be a clear plan before any agent starts working. If no plan exists, create one first using /plan-feature.

2. Define contracts first — The lead MUST define:

   • Database schema / data models
   • API interfaces (request/response shapes)
   • Component props / interfaces
   • Shared types

3. Assign file ownership — Each teammate owns specific directories. NO overlap. Two agents editing the same file = overwrites.

Team Spawn Template

Create an agent team to implement [feature].

Contracts (all teammates receive these):
[paste contracts here]

Teammates:
- Backend (Sonnet): Owns src/api/, src/models/, src/services/
  Task: Implement API endpoints and business logic

- Frontend (Sonnet): Owns src/components/, src/pages/
  Task: Implement UI components and pages

- Tests (Sonnet): Owns tests/
  Task: Write tests for both backend and frontend
  Blocked by: Backend and Frontend

Rules:
- Each teammate works ONLY in their owned directories
- Backend defines API contract FIRST, then all work in parallel
- Require plan approval before implementation
- Use Sonnet for all teammates

Post-build

After the team finishes:

1. Lead synthesizes all changes
2. Run full test suite
3. Delegate to code-reviewer for final review