orchestrator

Coordinate autonomous worker agents to execute beads for an epic.

1|Updated Feb 3, 2026

Search Tags:#automation #workflow #beads #multi-agent #parallel #orchestrator #epic

Ready to run

npx skills add https://github.com/trungtnm/claude-code-utils --skill orchestrator-trungtnm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/trungtnm/claude-code-utils/tree/main/plugins/skills/orchestrator
Command: npx skills add https://github.com/trungtnm/claude-code-utils --skill orchestrator-trungtnm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and coordinate multi-agent bead execution. Use when starting a new epic, assigning tracks to agents, or monitoring parallel work progress.

Core Features & Use Cases

Spawns and monitors parallel worker agents that execute beads autonomously.
Coordinates cross-track dependencies, progress reporting, and artifact delivery across tracks.
Provides structured phases for planning, spawning workers, monitoring, review, and completion.

Quick Start

Spawn an orchestrator to coordinate beads for an epic and monitor the associated tracks.

Frequently Asked Questions about orchestrator

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

FAQPage Schema

How do I coordinate multi-agent workflows with cross-track dependencies?▼

Multi-agent workflow coordination requires an orchestrator to spawn parallel worker agents, monitor their progress, handle blockers, and aggregate deliverables across all tracks. This enforces explicit steps for planning, execution, verification, and artifact persistence.

What is the best way to manage parallel worker agents executing beads for an epic?▼

Managing parallel worker agents for an epic involves structured phases: planning tracks, spawning autonomous workers, monitoring progress, conducting quality checks, and completing artifact delivery. Cross-track communication is enforced to resolve dependencies.

When do I need multi-agent orchestration for automation workflows?▼

You need multi-agent orchestration for automation workflows when an epic involves multiple tracks with cross-track dependencies. It coordinates planning, worker spawning, progress monitoring, blocker handling, and final deliverable aggregation.

Can I use this orchestrator to handle blockers and verify bead completion autonomously?▼

Yes, the orchestrator handles blockers and verifies bead completion autonomously. It enforces explicit orchestration steps including quality checks, cross-track communication, and artifact persistence to ensure all worker agents meet defined epic requirements.

Does multi-agent orchestration support artifact persistence and progress reporting across tracks?▼

Multi-agent orchestration supports artifact persistence and progress reporting. It coordinates cross-track dependencies, monitors parallel worker agents, and enforces artifact delivery to ensure all epic deliverables are aggregated and verified.

Why use a dedicated orchestrator instead of manually managing parallel worker agents?▼

A dedicated orchestrator enforces explicit steps for planning, spawning workers, monitoring progress, and verifying bead completion. Manually managing parallel agents risks missing cross-track dependencies, quality checks, and artifact persistence required for complex epics.