orchestrator-multiagent

Coordinate autonomous multi-agent software initiatives with Agent Teams and Beads tracking.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bjornslib/cobuilder-harness --skill orchestrator-multiagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-multiagent
Source: https://github.com/bjornslib/cobuilder-harness/tree/main/.claude/skills/orchestrator-multiagent
Command: npx skills add https://github.com/bjornslib/cobuilder-harness --skill orchestrator-multiagent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill coordinates autonomous, multi-agent workflows to orchestrate software development with persisted worker teams, Beads-based task tracking, and phase-driven progress.

Core Features & Use Cases

  • Worker delegation: spawn and coordinate specialized teammates (frontend/backend/testing) to implement features.
  • Beads-driven progress: manage tasks, dependencies, and status across Uber-epics and epics.
  • Autonomous progression: enable multi-feature sessions with validations and handoffs to System 3.

Quick Start

Initiate an autonomous multi-feature session by invoking the orchestrator-multiagent skill and allowing it to manage worker teams and beads.

Frequently Asked Questions about orchestrator-multiagent

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

FAQPage Schema
How do I coordinate multiple autonomous agents for software development workflows?

Multi-agent orchestration coordinates autonomous software workflows by spawning specialized worker teams, tracking tasks with Beads, and applying three-phase planning, execution, and validation gates across epics and uber-epics.

What is Beads task tracking and how does it manage multi-agent progress?

Beads task tracking manages multi-agent progress by persisting task state, dependencies, and status across uber-epics and epics, enabling memory-driven decisions and autonomous progression throughout the software development lifecycle.

How do I spawn and delegate tasks to specialized worker teams in a multi-agent system?

Worker delegation spawns specialized teammates like frontend, backend, and testing workers, using TaskCreate and SendMessage to assign tasks, manage cross-epic dependencies, and coordinate parallel execution within the orchestration workflow.

Does multi-agent orchestration support parallel workers and cross-epic dependencies?

Multi-agent orchestration supports parallel workers and cross-epic dependencies by applying autonomous progression rules, memory-driven decisions, and integrated validation gates to coordinate complex, multi-feature software sessions.

What are the three-phase workflows in autonomous multi-agent orchestration?

The three-phase workflows in multi-agent orchestration are planning, execution, and validation, enabling autonomous progression with regression checks and handoffs to manage software initiatives from uber-epics down to individual epics.

When should I use autonomous multi-agent orchestration instead of single-agent task execution?

Autonomous multi-agent orchestration is ideal for complex software initiatives requiring parallel workers, specialized team delegation, and cross-epic dependency management, whereas single-agent execution suits simpler, isolated tasks without coordinated validation gates.