pal-e-docs

Board: Worktree Isolation for Parallel Agents

board-188-worktree-isolation Board

active
Project

Board: Worktree Isolation for Parallel Agents

Decomposition of pal-e-platform#188 — 7 AC across 3 systems (claude-custom code, pal-e-docs SOPs, pal-e-platform CLAUDE.md).

Parent

Board item #418 on board-pal-e-agency. Forgejo issue: forgejo_admin/pal-e-platform#188. Dev work vs docs work split.

User Stories

Role Key Story Success Metric
Dev agent dev-execute I want my worktree to be isolated so parallel agents don't conflict Two agents on the same repo produce clean, non-conflicting PRs

Architecture

  • arch:hooks — SessionStart or agent-spawn hook that creates /tmp worktrees
  • arch:agent-spawn — agent profile updates for cross-repo clone behavior

Acceptance Criteria

  • Spawned dev agents work in /tmp clones, not the main checkout
  • SOPs document the worktree isolation pattern

Kanban

  • Dev: hook + agent profile — Create worktree isolation hook in claude-custom. AC 1,2,5,6,7 from parent. ~5 min.
  • Dottie: SOP updates — Update worktree-workflow and agent-spawn-conventions. AC 3,4 from parent. ~3 min.