orchestrator

Coordinate multi-agent beads to execute epics with progress reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate the execution of epics by coordinating multiple agent beads, aligning plans, handling blockers, and providing cohesive progress visibility across tracks.

Core Features & Use Cases

  • Phase-driven orchestration: read the execution plan, initialize agent mail, spawn worker subagents, monitor progress, and resolve cross-track blockers.
  • Parallel track management: coordinate multiple tracks simultaneously, ensuring synchronization and timely updates for each bead.
  • Epic completion workflow: aggregate track progress and trigger completion actions with centralized reporting.

Quick Start

Spawn and monitor worker actors from the execution plan to coordinate epic progress.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I coordinate multiple agents to execute epics in parallel?

Multi-agent orchestration coordinates parallel tracks by reading execution plans, spawning worker subagents, and synchronizing progress across teams. This ensures efficient epic completion by handling blockers and aggregating updates from multiple agents.

What is multi-agent orchestration for parallel track management?

Multi-agent orchestration is the process of coordinating multiple tracks simultaneously to ensure synchronization and timely updates. It manages worker subagents to execute epics, aligning plans and resolving cross-track blockers for cohesive progress visibility.

How do I monitor progress and resolve blockers across coordinated agent tracks?

To monitor progress and resolve blockers, the orchestration workflow initializes agent mail, tracks worker subagent updates, and resolves cross-track issues centrally. This ensures synchronization and timely updates for each bead in the execution plan.

Do I need a predefined execution plan to start spawning worker subagents?

Yes, a predefined execution plan is required to start spawning and monitoring worker subagents. The orchestration process reads the execution plan first to initialize agent mail, spawn workers, and coordinate epic progress effectively.

Best way to handle cross-track blockers during epic completion?

The best way to handle cross-track blockers during epic completion is using phase-driven orchestration to monitor progress and resolve issues centrally. It aggregates track progress and triggers completion actions with centralized reporting.

When should I use orchestrated parallel tracks instead of single-agent execution?

Use orchestrated parallel tracks instead of single-agent execution when projects require coordinated multi-agent synchronization, blocker handling, and progress reporting across multiple teams. This approach ensures cohesive epic completion with centralized visibility.