using-worktreeslisted

# Using Worktrees ## Overview Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching. **Core principle:** Systematic directory selection + safety verification = reliable isolation. ## Scope This skill covers git worktree setup, lifecycle, and known limitations for rageatc-code-oss workflows. It does NOT cover process-level isolation (Docker sandboxes), CI/CD pipeline isolation, or worktree usage outside of chunk-based development. ## When to Use - **Standard/Thorough workflows:** Each implementation chunk gets its own worktree for isolation - **Parallel chunks (Thorough only):** Multiple worktrees enable simultaneous work on chunks with non-overlapping file sets - **Quick workflow:** Optional — branch-based isolation may suffice for single small changes ## Approach: Orchestrator-Managed Worktrees The orchestrator creates and manages worktrees manually using `git worktree add`, then points developer-agents to the worktree directory. **Why manual, not automated:** Claude Code's `isolation: "worktree"` option creates a fresh worktree per agent spawn with an opaque branch name. The manual approach keeps the lifecycle with the orchestrator — setup (baseline tests, `.gitignore` checks) runs in the worktree before the agent launches, review iterations reuse the same worktree across developer invocations, and branches are named after chunks. The Feb 2026 bugs that originally forced this choic