Git Worktree Manager

Manage parallel development across ALL projects using git worktrees with Claude Code agents. Each worktree is an isolated copy of the repo on a different branch, stored centrally at the configured worktreeBase directory.

Trigger Phrases

• "spin up worktrees for X, Y, Z"
• "spin up worktrees for X, Y, Z with prompt '...'"
• "create worktrees for features A, B, C"
• "new worktree for feature/auth"
• "worktree status" / "show all worktrees"
• "cleanup worktrees" / "clean up the auth worktree"
• "launch agent in worktree X"

File Locations

File	Purpose
~/.claude/claude-spec.config.json	User config - your personal terminal, shell, port range settings
~/.claude/worktree-registry.json	Global registry - tracks all worktrees across all projects
../../claude-spec.config.json	Default config - template at plugin root used when user config doesn't exist
./scripts/	Helper scripts - port allocation, registration, launch, cleanup

First-Time Setup

When this skill is first used and ~/.claude/claude-spec.config.json doesn't exist, run the interactive setup:

Step 1: Detect Shell

DETECTED_SHELL=$(basename "$SHELL")
echo "Detected shell: $DETECTED_SHELL"

Step 2: Ask Configuration Questions

Use the AskUserQuestion tool with these questions:

Question 1 - Terminal:

header: "Terminal"
question: "Which terminal do you use for development?"
options:
  - label: "iTerm2 (Recommended for macOS)"
    description: "macOS terminal with excellent tab support"
  - label: "Ghostty"
    description: "Fast, GPU-accelerated terminal"
  - label: "tmux"
    description: "Terminal multiplexer (creates detached sessions)"
  - label: "Other"
    description: "WezTerm, Kitty, or Alacritty"

Question 2 - Shell:

header: "Shell"
question: "What shell do you use? (detected: ${DETECTED_SHELL})"
options:
  - label: "${DETECTED_SHELL} (Recommended)"
    description: "Your current default shell"
  - label: "bash"
    description: "Bourne Again Shell"
  - label: "zsh"
    description: "Z Shell (macOS default)"
  - label: "fish"
    description: "Friendly Interactive Shell"

Question 3 - Claude Command:

header: "Claude"
question: "How do you launch Claude Code?"
options:
  - label: "claude --dangerously-skip-permissions (Recommended)"
    description: "Auto-approves tool use for worktree agents"
  - label: "cc"
    description: "Common alias for Claude Code"
  - label: "claude"
    description: "Standard command without auto-approve"

Question 4 - Worktree Base:

header: "Location"
question: "Where should worktrees be created?"
options:
  - label: "~/Projects/worktrees (Recommended)"
    description: "Keeps worktrees separate from source repos"
  - label: "~/worktrees"
    description: "Shorter path in home directory"

Step 3: Write Config File

After collecting answers, write the config:

mkdir -p ~/.claude
cat > ~/.claude/claude-spec.config.json << EOF
{
  "terminal": "${TERMINAL_ANSWER}",
  "shell": "${SHELL_ANSWER}",
  "claudeCommand": "${CLAUDE_CMD_ANSWER}",
  "worktreeBase": "${WORKTREE_BASE_ANSWER}",
  "portPool": { "start": 8100, "end": 8199 },
  "portsPerWorktree": 2,
  "registryPath": "~/.claude/worktree-registry.json",
  "defaultCopyDirs": [".agents", ".env.example", ".env"],
  "healthCheckTimeout": 30,
  "healthCheckRetries": 6
}
EOF

echo "Configuration saved to ~/.claude/claude-spec.config.json"

Terminal Answer Mapping

User Selection	Config Value
iTerm2 (Recommended for macOS)	iterm2-tab
Ghostty	ghostty
tmux	tmux
Other (WezTerm)	wezterm
Other (Kitty)	kitty
Other (Alacritty)	alacritty

Reconfiguration

To reconfigure at any time, run: /claude-spec:worktree-setup

Quick Start

1. Check Status

./scripts/status.sh
./scripts/status.sh --project my-project

2. Create a Worktree

# Allocate ports
PORTS=$(./scripts/allocate-ports.sh 2)

# Create git worktree
git worktree add ~/Projects/worktrees/my-project/feature-auth -b feature/auth

# Register it
./scripts/register.sh my-project feature/auth feature-auth \
  ~/Projects/worktrees/my-project/feature-auth \
  /path/to/repo \
  "8100,8101" "Implement OAuth"

# Launch Claude agent
./scripts/launch-agent.sh ~/Projects/worktrees/my-project/feature-auth "Implement OAuth"

3. Cleanup

./scripts/cleanup.sh my-project feature/auth
./scripts/cleanup.sh my-project feature/auth --delete-branch

Scripts Reference

allocate-ports.sh

Allocate N unused ports from the global pool (default: 8100-8199).

./scripts/allocate-ports.sh <count>
# Returns: space-separated port numbers (e.g., "8100 8101")

register.sh

Register a worktree in the global registry.

./scripts/register.sh <project> <branch> <branch-slug> <worktree-path> <repo-path> <ports> [task]

launch-agent.sh

Launch Claude Code in a new terminal for a worktree.

./scripts/launch-agent.sh <worktree-path> [task] [--prompt "template"] [--headless]

Prompt Modes:

• --prompt "template" - Interactive mode (default): prompt pre-filled in Claude's input
• --prompt "template" --headless - Headless mode: auto-executes immediately with -p flag

Template Variables:

• {{service}} / {{branch_slug}} - Branch slug (e.g., "feature-auth")
• {{branch}} - Full branch name (e.g., "feature/auth")
• {{project}} - Project name
• {{worktree_path}} - Full worktree path
• {{port}} - First allocated port
• {{ports}} - All ports (comma-separated)

status.sh

Show status of all managed worktrees.

./scripts/status.sh [--project <name>]

cleanup.sh

Full cleanup of a worktree (ports, directory, registry, optionally branch).

./scripts/cleanup.sh <project> <branch> [--delete-branch]

release-ports.sh

Release ports back to the global pool.

./scripts/release-ports.sh <port1> [port2] ...

Configuration

Your personal settings are stored at ~/.claude/claude-spec.config.json.

To set up or reconfigure: run /claude-spec:worktree-setup or follow the First-Time Setup section above.

Example config:

{
  "terminal": "iterm2-tab",
  "shell": "zsh",
  "claudeCommand": "cc",
  "worktreeBase": "~/Projects/worktrees",
  "portPool": { "start": 8100, "end": 8199 },
  "portsPerWorktree": 2,
  "registryPath": "~/.claude/worktree-registry.json",
  "defaultCopyDirs": [".agents", ".env.example", ".env"],
  "healthCheckTimeout": 30,
  "healthCheckRetries": 6
}

Terminal options: ghostty, iterm2, iterm2-tab, tmux, wezterm, kitty, alacritty

Config lookup precedence:

1. User config: ~/.claude/claude-spec.config.json
2. Plugin default: ./claude-spec.config.json (plugin root)
3. Hardcoded defaults

Global Registry Schema

Location: ~/.claude/worktree-registry.json

{
  "worktrees": [
    {
      "id": "unique-uuid",
      "project": "my-project",
      "repoPath": "/path/to/repo",
      "branch": "feature/auth",
      "branchSlug": "feature-auth",
      "worktreePath": "/Users/.../worktrees/my-project/feature-auth",
      "ports": [8100, 8101],
      "createdAt": "2025-12-04T10:00:00Z",
      "validatedAt": null,
      "agentLaunchedAt": null,
      "task": "Implement OAuth login",
      "prNumber": null,
      "status": "active"
    }
  ],
  "portPool": {
    "start": 8100,
    "end": 8199,
    "allocated": [8100, 8101]
  }
}

Common Workflows

Parallel Development

When user says "spin up worktrees for feature/a, feature/b, feature/c":

1. Read user config (or template fallback) to get terminal and claude command settings
2. Allocate ports for all worktrees upfront
3. For each branch (can parallelize):
   • Create git worktree
   • Copy required directories (.agents, .env, etc.)
   • Install dependencies
   • Validate (optional health check)
   • Register in global registry
   • Launch Claude agent
4. Report summary with paths and ports

Initial Prompts

Launch agents with pre-configured prompts:

# Interactive - prompt ready in input
./scripts/launch-agent.sh ~/worktrees/proj/auth "" --prompt "/explore"

# Headless - auto-executes
./scripts/launch-agent.sh ~/worktrees/proj/auth "" --prompt "/review-code" --headless

# With template substitution
./scripts/launch-agent.sh ~/worktrees/proj/auth "" --prompt "analyze {{service}}"

Safety Guidelines

1. Before cleanup, check PR status (merged = safe, open = warn)
2. Before deleting branches, confirm no uncommitted work
3. Port conflicts: If port in use by non-worktree process, pick different port
4. Max worktrees: With 100-port pool and 2 ports each, max ~50 concurrent worktrees

Troubleshooting

"Worktree already exists"

git worktree list
git worktree remove <path> --force
git worktree prune

"Port already in use"

lsof -i :<port>
# Kill if stale, or pick different port

Registry out of sync

# Compare registry to actual worktrees
cat ~/.claude/worktree-registry.json | jq '.worktrees[].worktreePath'
find ~/Projects/worktrees -maxdepth 2 -type d