Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task…
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. Tool Boundary If a task says to use Orca orchestration, the coordinator must create Orca runtime state with orca orchestration task-create and orca orchestration dispatch --inject or orca orchestration run. Do not substitute non-Orca subagent tools, generic agent-spawn APIs, or chat-only parallel worker features. Those may create useful workers, but they do not create Orca task/dispatch provenance, injected lifecycle preambles, worker_done authority, or decision gates. Before claiming a worker was orchestrated, verify the task/dispatch exists: orca orchestration task-list --json orca orchestration dispatch-show --task <task_id> --json
don't have the plugin yet? install it then click "run inline in claude" again.