shared-worktree

Git worktrees isolate code changes in per-agent directories to prevent cross-agent conflicts during parallel development. Each agent works in a dedicated worktree and coordinates merging at checkpoints to maintain isolation and traceability.

Agent-specific git worktrees require the {agent}-worktree naming convention to maintain isolation and traceability. Correct worktree naming ensures coordinated merging at checkpoints and prevents cross-agent conflicts during parallel development workflows.

To merge code changes from separate git worktrees, stage edits within the designated worktree, validate against the main branch, and coordinate merging at checkpoints. This synchronized workflow prevents cross-agent conflicts and preserves traceability.

Yes, multiple agents can modify shared code in parallel without overwriting each other by using isolated git worktrees. This workflow prevents cross-agent conflicts by keeping iterative changes in separate per-agent directories until checkpoint merging.

Yes, a configured Git repository is required to start an agent workflow with isolated worktrees. The repository provides the necessary branching structure to enforce the {agent}-worktree naming convention and coordinate synchronized merges at checkpoints.

Git worktrees for parallel agent development require strict adherence to workflow rules and the {agent}-worktree naming convention to maintain isolation. Without synchronized validation and coordination at checkpoints, traceability and cross-agent conflict prevention can break down.