worktrees:orchestrator

To coordinate parallel subagents using git worktrees, an orchestrator creates and manages separate worktrees for each subtask, enabling isolated execution. It tracks progress and merges results in dependency order before cleanup.

Running parallel development tasks without git branch conflicts is best achieved by using isolated git worktrees for each feature. This orchestrator creates separate worktrees for subagents, keeping state isolated and ensuring orderly merges.

Git worktree orchestration works by creating a main agent that manages multiple subagents in separate worktrees. It handles feature branch creation, progress tracking via commit logs, and merges results sequentially before cleaning up.

You do not need existing feature branches to start orchestrating parallel worktrees. You invoke the orchestrator with a feature name, and it creates per-feature worktrees dynamically using git worktree add commands.

To clean up git worktrees after merging parallel subagent tasks, the orchestrator merges results in dependency order and then performs worktree cleanup. It monitors progress with git worktree list before safely removing isolated environments.