using-worktreeslisted

# Using Worktrees Shipyard isolates parallel task execution in git worktrees so concurrent subagents don't clobber each other's edits. **Trust the platform** — pass `isolation: worktree` on the Agent call and let Claude Code handle creation, cwd, and cleanup. **Render before asking.** Before any AskUserQuestion, render the decision context as assistant chat text. Content that exists only in a Read result, a subagent/Agent return, or the question/option strings **does not count as rendered** (the UI shows a compact card) — restate it in chat first. ## When to Use Worktrees | Mode | Use worktrees? | |---|---| | Solo (1–3 tasks per wave, sequential) | No — tasks run on the working branch, one after another | | Subagent / parallel (4+ tasks per wave, concurrent) | **Yes** — one worktree per task | | Team mode (10+ tasks, persistent feature tracks) | **Yes** — one worktree per feature track | | `/ship-review` diff inspection | Optional — read-only; worktree only if reviewing across branches | | Hotfix | No — work on the user's current branch directly | | `/ship-quick` | No — single change, working branch | The rule of thumb: **isolate when concurrency would otherwise race**. Sequential work doesn't need worktrees. ## How to Create a Worktree (the New, Simple Way) The orchestrator dispatches a subagent with `isolation: "worktree"` on the `Agent` call: ``` Agent( subagent_type: "general-purpose", isolation: "worktree", prompt: <task-loop prompt template, parameterized>