team

Team Execution

Spawn teammates in isolated worktrees for parallel implementation. Each teammate gets one task, works independently, and reports back.

This is for parallel implementation of independent tasks. For analysis (review, opinion, plan) - use their dedicated commands.

IMPORTANT: If the spec below invokes any deferred tool (e.g. AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.

Step 1: Determine Subcommand

If argument provided (e.g., /lets:team run), parse it:

• run -> go to Run (pass remaining flags like --tasks A,B,C to Step R2)
• status -> go to Status
• stop -> go to Stop

If no argument, use AskUserQuestion:

AskUserQuestion(
  questions=[{
    question: "What do you want to do with the team?",
    header: "Team",
    options: [
      { label: "Run", description: "Launch teammates to implement tasks in parallel" },
      { label: "Status", description: "Show active team progress" },
      { label: "Stop", description: "Stop active team and preserve branches" }
    ],
    multiSelect: false
  }]
)

---

Run

Launch a parallel team. Select tasks, spawn teammates, monitor progress, merge results.

Step R1: Guards

# Guard 1: not in worktree
GIT_DIR=$(git rev-parse --git-dir 2>/dev/null)
# If GIT_DIR contains "worktrees/" -> stop: "Teams must be created from the main repo, not a worktree."

# Guard 2: no active team
ls ~/.claude/teams/ 2>/dev/null | grep "lets-team"
# If any lets-team-* dirs exist -> stop: "Active team found. Use /lets:team status or /lets:team stop first."

# Guard 3: clean working directory
git status --short
# If dirty -> warn: "Uncommitted changes detected. Commit or stash before running a team."

Step R2: Get Tasks

Two input modes:

1. Interactive (default): Show ready tasks and let user pick.

ready limit=10