auto-team

Auto Team

Orchestrate parallel agent work using native TeamCreate, TaskCreate, and Agent tools with worktree isolation. Each teammate works in an isolated git worktree; results merge into an integration branch.

When to Use

ALL must be true:

• 3+ independent parts that can run in parallel
• Parts touch different files/modules (no shared-file edits)
• Task would take >30 min sequentially

Do NOT use when:

• Single file edit, small bug fix, simple feature
• Parts depend on each other sequentially
• User explicitly wants single-session work
• Dirty working tree (commit or stash first)

digraph decision {
  "3+ independent parts?" [shape=diamond];
  "Touch different files?" [shape=diamond];
  ">30 min sequential?" [shape=diamond];
  "Use auto-team" [shape=box];
  "Use single session" [shape=box];

  "3+ independent parts?" -> "Touch different files?" [label="yes"];
  "3+ independent parts?" -> "Use single session" [label="no"];
  "Touch different files?" -> ">30 min sequential?" [label="yes"];
  "Touch different files?" -> "Use single session" [label="no"];
  ">30 min sequential?" -> "Use auto-team" [label="yes"];
  ">30 min sequential?" -> "Use single session" [label="no"];
}

---

Workflow

Phase 0: Preflight (NEVER skip)

git rev-parse --git-dir        # Must be a git repo
git status --porcelain          # Must be clean — if dirty, ask user to commit/stash
git branch --show-current       # Record as ORIGINAL_BRANCH for rollback
git worktree list               # Check no conflicts

Stop and inform user if any check fails.

Phase 1: Plan & Approve

Present plan to user, wait for confirmation:

I'll split this into [N] parallel tasks:

1. [task] -> feature/[name] (opus — complex logic)
2. [task] -> feature/[name] (sonnet — implementation)
3. [task] -> feature/[name] (sonnet — tests)

Integration branch: feature/integration-[project]
Cost: ~[N]x single session tokens

Proceed?

3-4 teammates max for cost efficiency.

Phase 2: Create Integration Branch