name: workflow-team description: | Workflow for Agent Teams autonomous parallel development. Provides team lead orchestration guide and teammate execution protocol. Covers file ownership, communication, and merge strategy. argument-hint: "[lead|teammate]"

Agent Teams Workflow

Autonomous parallel development workflow for Agent Teams. Invoke with: /workflow-team lead or /workflow-team teammate

For Team Lead (/workflow-team lead)

Phase 1: Plan

After plan approval, create tasks via TaskCreate and spawn teammates immediately. No separate confirmation needed.

Phase 2: Execute (after user approval)

Enable Plan Approval for complex/risky tasks. All teammates work on the same feature branch (file ownership prevents conflicts).

Spawn Example

Create an agent team with N teammates:
1. "{name}" — Read {task-file-path}. Own files: {file-list}.
2. "{name}" — Read {task-file-path}. Own files: {file-list}.
Use Opus for all teammates. Require plan approval.

Phase 3: Review & Merge (after all teammates complete)

Merge Strategy

main
 └── development
      └── {working-branch}  ← single branch, all teammates work here
           ├── teammate-A commits (owns: file-list-A)
           ├── teammate-B commits (owns: file-list-B)
           └── teammate-C commits (owns: file-list-C)

After all teammates done → Phase 3

Git Conventions

See workflow-commits.md

For Teammates (/workflow-team teammate)

Execution Steps

Teammate Rules

• ONLY modify files assigned to you
• NEVER touch files owned by another teammate
• Shared files (barrel index.ts, routes.ts): message lead before modifying
• New files: create freely within your task scope
• Do NOT create branches — work on the feature branch created by lead

Failure Recovery (Autonomous)

IF any step fails:
  1. Log to docs/reports/failures/{teammate-name}-{timestamp}.md
  2. Retry SAME approach (1 attempt)
  3. Retry DIFFERENT approach (1 attempt)
  4. After 3 failures:
     → Message lead: "Blocked on [issue]. Attempted [approaches]."
     → Pick up next available task
     → DO NOT STOP

Communication

Cost Notes

• Use opus model for teammates
• Teammates: NO code-reviewer — TDD cycle is the quality gate, lead handles all review in Phase 3
• Lead runs code-reviewer + e2e-tester as the single review gate post-merge
• Minimize sub-agent calls per teammate
• Avoid broadcast messages — message lead directly