orchestration

# Orca Inter-Agent Orchestration Orchestration is Orca's structured coordination layer for agent messages, task ownership, dispatch state, and worker completion tracking. Use this skill when coordination state matters. For lightweight terminal prompts or basic worktree/terminal/built-in-browser control, use `orca-cli`. ## When To Use - Send/reply/ask between agent terminals with persistent messages. - Dispatch structured tasks to workers and wait for `worker_done` or `escalation`. - Track task DAGs with dependencies. - Run coordinator loops or decision gates. ## Preconditions - `orca status --json` should show a running runtime. - `orca` must be on PATH (`orca-ide` on Linux). - The orchestration experimental feature must be enabled in Settings > Experimental. - `orca orchestration` commands are RPC calls to the running Orca runtime. ## Ownership Orchestration messages and tasks are runtime-global. Completion authority comes from the active dispatch context: `taskId` + `dispatchId` + assignee handle. Classify inherited context before sending lifecycle messages: - Coordinated subtask: a live coordinator owns the DAG and waits on this dispatch. Follow the preamble exactly, including `worker_done`, heartbeat/status, `ask`, and `escalation`. - Full handoff: the original actor delegated ownership and is not monitoring. Finish in the current session. Create a new coordinator only when the user asks or you deliberately decompose fresh subtasks; if spawning workers, use your...