orchestration

Coordinates Orca workers with threaded messages, task DAGs, and decision gates.

1|Updated May 3, 2021
One-click install
npx skills add https://github.com/leogurja/dotfiles --skill orchestration-leogurja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/leogurja/dotfiles/tree/main/home/dot_agents/skills/orchestration
Command: npx skills add https://github.com/leogurja/dotfiles --skill orchestration-leogurja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI agents manually leads to lost context, duplicated work, and unclear ownership. This Skill provides structured multi-agent coordination through Orca, so tasks are dispatched, supervised, and completed with explicit state tracking. ## Core Features & Use Cases - Structured Agent Coordination: Send threaded messages, run blocking ask/reply flows, and dispatch tasks to supervised Orca workers. - Task DAGs and Decision Gates: Decompose work across agents, wait on worker_done or escalation events, and run coordinator loops with conditional gates. - Version-Matched Guidance: Loads the orchestration reference directly from the installed Orca binary via ORCA skills get orchestration, so instructions never drift from the runtime. - Use Case: Split a large refactor into subtasks, assign each to an Orca worker, monitor completion events, and gate the merge step on all workers reporting done. ## Quick Start Ask the assistant to decompose your project into tasks and coordinate Orca workers to complete them, starting by loading the guide with the resolved Orca executable.

Frequently Asked Questions about orchestration

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

FAQPage Schema
How do I coordinate multiple AI agents with Orca?▼

Use the Orca orchestration flow: resolve the correct executable, run ORCA skills get orchestration to load the version-matched guide, then dispatch tasks, send threaded messages, and wait on worker_done events. The guide covers the standard local coordinator loop.

When should I use orchestration instead of an Orca handoff?▼

Use orchestration when you need to supervise, monitor, or coordinate a DAG of tasks across agents. Use orca-cli handoffs for full ownership transfers like "hand off" or "give this to another agent" when no ongoing supervision is required.

Which Orca executable should I run on Linux?▼

On Linux outside an Orca-managed terminal, use orca-ide. Never run bare orca there, since it usually resolves to the GNOME Orca screen reader and starts speech. Prefer ORCA_CLI_COMMAND when set, or orca-dev in a dev checkout.

What happens if the Orca binary is not running?▼

If a command reports Orca is not running, start it with ORCA open --json and retry. If the selected executable cannot run at all, report its exact error and stop rather than falling through to a different binary.

How do I load conditional orchestration references?▼

Run ORCA skills get orchestration --reference references/<file>.md for the specific gate you need, listing names with --references. If the binary rejects --reference, use --full and read the named bundled reference before acting.