beads-orchestrator

Multi-agent orchestration with parallel git worktrees is managed by coordinating Beads tasks end-to-end, assigning per-task worktrees and branches to specialized agents, and serializing merges through a single integrator.

To prevent merge conflicts across agents during parallel task execution, the orchestration loop enforces per-task worktrees and branches, routing all final merges through a single integrator that serializes commits while recording progress to Beads.

Yes, you need git, bd, and tmux installed to run multi-agent task management, as the Skill relies on these dependencies to manage worktrees, execute specialized agent tasks, and coordinate the orchestration loop.

The orchestration loop handles task handoffs by enforcing a one-active-task-per-agent model, passing architected plans from the planner to workers, then routing outputs to reviewers and QA agents before final serialized merges.

Multi-agent serialized merges can fail due to integration conflicts or agent task errors, but the orchestration loop provides robust recovery paths to resume the workflow and ensure safe merges to the main branch.

Yes, you can use beads-orchestrator to manage UI QA and code reviews, as it coordinates these specialized agent roles within the workflow before passing results to the single integrator for final serialized merges.