project-orchestrator:worktree

Git worktrees isolate parallel plan implementations by mapping each plan slug to a dedicated working directory, preventing file collisions. The system auto-detects monorepo or polyrepo setups and runs per-service configuration in each isolated branch.

Yes, git worktrees support polyrepo setups by auto-detecting the repository structure and running per-service setup in the appropriate isolated worktree. This enables concurrent plan execution across multiple repositories without file collisions.

To manage worktree creation failures, the system validates branches explicitly and handles creation failures directly. It checks worktree health, updates the living state document with created paths, and returns the final worktree paths to the caller.

The best way to track created worktree paths is by updating a living state document. The system records all created worktree paths in this design doc, ensuring isolated parallel plans remain synchronized and traceable throughout execution.

No, setting up isolated git worktrees does not require manual per-service configuration. The system auto-detects the repository structure and automatically applies the necessary per-service setup within the appropriate worktree.