experiment

Run a parallel experiment: $ARGUMENTS

Purpose

Test multiple competing approaches to the same problem simultaneously. Each approach gets its own git worktree and sub-agent. Results are compared at the end so the best approach can be merged.

This is NOT for parallelizing parts of one plan (use /workflows-work for that). This is for when you genuinely don't know which approach is best and want to try all of them.

Process

Phase 1: Define Tracks (orchestrator does this)

Parse the input (a gap analysis, a list of alternatives, a brainstorm, or a user description) and produce a track list:

TRACK DEFINITION
================
Base branch: <current branch or specified base>

Track A: <name>
  Branch: exp/<slug-a>
  Approach: <1-2 sentence description>
  Files touched: <predicted file list>
  Effort: low | medium | high

Track B: <name>
  Branch: exp/<slug-b>
  ...

[up to 5 tracks]

Conflict check: If two tracks modify the same files in incompatible ways, flag this to the user before proceeding. Parallel experiments must be independent.

Present the track list to the user and wait for confirmation before proceeding.

Phase 2: Create Worktrees

For each track, create a worktree branching from the base:

# From the repo root
git worktree add ../<repo-name>-exp-<slug> -b exp/<slug>

Worktree naming convention: ../<repo-name>-exp-<slug> (sibling to the main repo directory).

Verify all worktrees were created:

git worktree list

Phase 3: Dispatch Sub-Agents (parallel)

Dispatch one sub-agent per track using the Agent tool. All independent tracks run in parallel.

Each sub-agent receives:

1. Working directory: The worktree path (CRITICAL — sub-agent must cd here)
2. Track definition: What to implement and why
3. Source context: Relevant file contents from the base branch (read before dispatching)
4. Acceptance criteria: What "done" looks like for this track
5. Instructions:
   • Work ONLY in your assigned worktree directory
   • Write tests for your changes
   • Run tests and report results
   • Commit your work to the worktree's branch
   • Return the structured summary (see format below)