create-team

Create Team

Creates a planner + implementer agent team for the current worktree session.

Workflow

Step 1: Determine team name

Run git branch --show-current to get the current branch name. Convert to kebab-case team name:

• Remove worktree- prefix if present
• Replace + with -
• Example: worktree-feat+electron-app → feat-electron-app

Step 2: Create the team

Call TeamCreate with:

• team_name: the derived team name
• description: "Planner + Implementer team"

Step 3: Spawn teammates (parallel)

Spawn both teammates in parallel using the Agent tool in a single message with two tool calls:

Planner:

• team_name: the team name
• name: "planner"
• description: "Planner - brainstorm and spec writing"
• prompt: Read the full content of templates/planner-prompt.md and pass it as the prompt
• run_in_background: true

Implementer:

• team_name: the team name
• name: "implementer"
• description: "Implementer - code and test writing"
• prompt: Read the full content of templates/implementer-prompt.md and pass it as the prompt
• run_in_background: true

Step 4: Loop setup

Send loop configuration via SendMessage:

• To "planner": If /writing-specs skill is available, "Run /loop 10m /writing-specs update spec to periodically check and update specs." Otherwise skip this loop setup.
• To "implementer": "After completing assigned work, check TaskList for new tasks. You can run /loop 10m check TaskList for unassigned tasks and report to team-lead to automate this."

Step 5: Display work guide

Read templates/work-guide.md and display the content to the user. Teammate colors are auto-assigned from a hardcoded palette and cannot be configured programmatically.

Fallback

If Agent tool + team_name parameter fails with internal error (known issue anthropics/claude-code#40270):

1. Inform the user about the issue
2. Suggest spawning teammates manually:
   • Open separate terminal windows
   • Run claude in each with the planner/implementer prompts
   • Use SendMessage for coordination

Notes

• Teammates are full Claude Code sessions, not subagents
• Both teammates can use all tools including Write, Edit, Bash
• Both can run skills like /writing-specs, /loop
• /loop is session-scoped and expires after 7 days
• Teammate colors are auto-assigned from hardcoded palette (red, blue, green, yellow...) — not configurable
• All communication flows through team-lead (planner <-> implementer direct messaging disabled by prompt rules)
• Teammate model defaults to standard Opus (no 1M context). To use 1M context, set env var before starting: export ANTHROPIC_DEFAULT_OPUS_MODEL='claude-opus-4-6[1m]'