shared-worktree-delegationlisted

# shared-worktree-delegation Delegating into a shared checkout is safe **only** with lanes and a gatekeeper parent. Without both, parallel agents overwrite each other and then gaslight the parent with partial greens. This skill is the **mechanics** of fanning out into one checkout. For which fan-out skill the work belongs to in the first place, read the route table in `parallel-subagent-implementation`. ## Parent means a session, not a nested child A **stage parent** is a separately launched top-level chat/session running one pipeline stage. It may dispatch one level of workers when its harness supports it. A worker may dispatch nothing — say so in its brief, because a worker that re-delegates puts the evidence two hops from the parent that has to verify it. A native child launched from another session is not a stage parent. The GitHub Project item, GitHub issue/PR artifacts, and handoffs bridge independent stage-parent sessions. The parent of every worker—whether the overall coordinator or a stage parent—must remain the gatekeeper and own external writes. ## Decide first: shared tree or isolated worktrees? | Use a shared tree | Use isolated worktrees (`isolation: "worktree"`) | |---|---| | Lanes are cleanly separable by directory/file | Agents must edit the same files | | Work is small and fast | Long refactors that churn shared modules | | You need one coherent tree at the end | You'll merge/cherry-pick results deliberately | Isolated worktrees cost real setup time a