using-git-worktrees

# using-git-worktrees OPTIONAL. Per-task filesystem isolation for parallel agent work — opt-in only, never the default path. Routed to by `subagent-driven-development` and `dispatching-parallel-agents` when, and only when, the caller requests isolation. If no isolation is requested, this skill does not run; parallel units share the working tree under their own discipline. Isolation is convenience, not soul. It lets concurrent units edit files without collision. It changes nothing about the gates — the consolidated work still clears `commit-gate` and the single `finishing-a-development-branch` terminal step, run by the caller. What it MUST NOT do is multiply that terminal step into one PR per unit. ## Pre-flight Read these, or STOP and surface the gap — never guess: - `<project-root>/.codearbiter/CONTEXT.md` — confirm the repo is a git repo and the base/working branch. - The discovered authoritative spec/plan pair for the caller's pipeline. Use its exact selected plan for the parallel unit list. Re-run the private bridge resolver `_resolve_workflow_pair` with the trusted project root and pipeline slug rather than reconstructing either path. For an HTML pair, load [includes/artifacts.md](../../includes/artifacts.md) and obtain HTML task and path records only through the installed engine `identity`, `index`, and symbol-scoped `read` operations. For a Markdown pair, use its existing Markdown task table. Worktree planning must not create, convert, or consult a c...