beads-orchestrator

Coordinate Beads tasks end-to-end with per-task worktrees and serialized merges.

Updated Jan 26, 2026

Search Tags:#beads #multi-agent #orchestration #merge #task-management #code-review #git-worktree

Ready to run

npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-orchestrator
Source: https://github.com/vega113/beads-orchestration-skills/tree/main/beads-orchestrator
Command: npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bd, tmux, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Beads orchestration coordinates multiple agents to complete Beads tasks from plan to merge, handling parallel worktrees, reviews, QA, and safe, serialized merges.

Core Features & Use Cases

End-to-end Beads task orchestration with per-task worktrees and serialized merges
Plan intake, architected plans, and task handoffs to specialized agents (planner, worker, reviewer, QA, integrator)
Enforces the one-active-task-per-agent model and robust recovery paths during failures

Quick Start

Start the orchestration by invoking beads-orchestrator to run the end-to-end Beads workflow.

Frequently Asked Questions about beads-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I orchestrate multi-agent workflows with parallel git worktrees?▼

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.

What is the best way to manage parallel task execution and prevent merge conflicts across agents?▼

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.

Do I need git and tmux to run multi-agent task management and code reviews?▼

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.

How does the orchestration loop handle task handoffs between planner, worker, reviewer, and QA agents?▼

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.

Why does multi-agent task orchestration fail during serialized merges, and how can I recover?▼

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.

Can I use beads-orchestrator to manage UI QA and code reviews for parallel development branches?▼

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.