agent-orchestration

Coordinate multiple agents for parallel tasks with dependency graphs and messaging.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/ejoliet/claude-skills --skill agent-orchestration-ejoliet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-orchestration
Source: https://github.com/ejoliet/claude-skills/tree/main/agent-orchestration
Command: npx skills add https://github.com/ejoliet/claude-skills --skill agent-orchestration-ejoliet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-agent orchestration using Claude Code's TeammateTool and Task system. Covers spawning agents (in-process, tmux, iTerm2 backends), TeammateTool operations, task dependency graphs, inbox/message passing, and shutdown protocols. Use when coordinating parallel code reviews, building pipeline workflows, running swarm patterns, or any divide-and-conquer agent task.

Core Features & Use Cases

  • Coordination of multiple agents (leader, teammates) across backends
  • Task dependency graphs and inbox-based messaging
  • Backends: in-process, tmux, or iTerm2 for parallel execution
  • Safe shutdown protocols and error handling

Quick Start

Create a leader, recruit teammates, and assign tasks with dependencies to orchestrate a small code-review swarm.

Frequently Asked Questions about agent-orchestration

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

FAQPage Schema
How do I coordinate multiple agents for parallel code reviews and task execution?

Multi-agent orchestration coordinates a leader agent with teammates across in-process, tmux, or iTerm2 backends to execute parallel tasks. It uses task dependency graphs and inbox-based messaging to manage divide-and-conquer workflows like parallel code reviews or swarm-based execution.

Can I use tmux or iTerm2 as execution backends for spawning multiple agents?

Yes, multi-agent orchestration supports in-process, tmux, and iTerm2 backends for parallel agent execution. These backends allow agents to run concurrently, enabling scalable task management and pipeline orchestration across separate terminal sessions.

What's the best way to set up task dependencies and inter-agent messaging in a distributed workflow?

Task dependency graphs and inbox-based message passing enable structured inter-agent communication in distributed workflows. The leader agent recruits teammates, assigns tasks with defined dependencies, and uses inbox routing to coordinate execution order and data handoffs.

When do I need multi-agent orchestration for pipeline workflows?

You need multi-agent orchestration when dividing complex tasks into parallel subtasks such as pipeline workflows, swarm-based execution, or modular backend operations. It applies when tasks require distributed coordination, inter-agent messaging, and scalable management across multiple concurrent agents.

How does error handling and shutdown work when coordinating a swarm of agents?

Multi-agent orchestration implements safe shutdown protocols and robust error handling to manage agent termination across all backends. The leader coordinates structured shutdown sequences, ensuring teammates complete or safely abort pending tasks during pipeline execution failures.

Does multi-agent orchestration require any external dependencies to run parallel tasks?

No external dependencies are required to run multi-agent orchestration for parallel tasks. It leverages Claude Code's built-in TeammateTool and Task system to manage agent spawning, task dependency graphs, and inter-agent messaging natively across supported backends.