intra-repo-parallel-work

Parallel development in a single git repository is coordinated by assigning tasks to multiple workers, isolating work in separate git worktrees, and managing touch-sets to avoid file conflicts.

A touch-set in git worktree isolation declares which specific files will be modified by a worker, managing dependencies and preventing multiple workers from touching the same resources and causing collisions.

You assign tasks to multiple workers by minting a unique worker ID, then using coordination commands to claim available items, which isolates each task in its own git worktree for safe parallel work.

Yes, work isolation requires the FS-GG coordination CLI tool in addition to git, enabling worker ID minting, task claiming, touch-set management, and worker communication when file overlaps occur.

The best way to handle concurrent feature development overlaps is by using the built-in worker communication channel provided by the coordination tool to resolve dependencies before merging isolated worktrees.

You should not use git worktrees for parallel work if your development workflow involves frequent concurrent updates to the exact same files, as touch-set management relies on declaring distinct file modifications to prevent conflicts.