What problem does it solve? When several agents or tasks work in one repository at once, they overwrite each other's files, long test runs pick up half-written edits, and merging everything back produces confusing conflicts. This Skill defines the rules for using git worktrees so parallel work stays isolated, verifications see a frozen tree, and branches merge back in a sane order. ## Core Features & Use Cases - Parallel agent isolation: One worktree and one task-named branch per agent, with disjoint file scopes, so concurrent work never silently clobbers another agent's edits. - Safe long-running verification: Guidance for the concurrency hazard where a harness sweeping stale worktrees deletes a live one mid-run, including a pid-file pattern to tell live checkouts from abandoned ones. - Ordered merge-back workflow: Merge one branch at a time in dependency order, regenerate build output instead of hand-merging it, and re-run tests after each merge. - Use Case: You coordinate three subagents fixing separate bugs in one repo. Each gets its own worktree under the shared worktrees root, branches from the same base, and you merge the branches back least-conflicting first, re-running the focused tests after each merge. ## Quick Start Create a separate git worktree and branch for each of my three agents under the standard worktrees directory, then merge their branches back one at a time in dependency order.
