Skip to main content
subagent CX Codex

multi-agent-coordinator · rohitg00 — Claude Code subagent: how to install

multi-agent-coordinator decomposes complex tasks into parallel branches, resolves dependencies, and merges outputs from multiple agents into coherent deliverables.

Apache-2.0 ★ 2,858 updated 2026-05-12

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/multi-agent-coordinator.md
Open on GitHub

What multi-agent-coordinator does

The subagent splits complex assignments into discrete units and structures them as a directed acyclic graph. Independent tasks execute in parallel while dependent ones wait for prerequisite inputs. If a worker drags out execution, an 80% quorum rule lets the pipeline advance with available outputs.

It supports five orchestration patterns. To prevent context overflow, it strips intermediate reasoning before forwarding data downstream. Merges follow explicit rules: concatenation for prose, unions for code edits, and expert priority for contradictory recommendations. It then runs tests, type checks, and linting through Bash.

Because the configuration specifies the opus model, running heavy parallel workloads will consume token allowances rapidly.

What it helps with

  • Split a large coding task into parallel branches with DAG dependencies
  • Merge file edits from multiple agents without overwriting changes
  • Prevent context saturation by pruning intermediate reasoning between steps
  • Detect and break circular dependencies before task execution starts

Example prompts for the agent

  • Coordinate refactoring across auth and billing using the Map-Reduce pattern
  • Run two agents in Debate mode to evaluate this architectural proposal
  • Break down the database migration task into a dependency graph and check for cycles

How to install multi-agent-coordinator

Manually: put the files in place

.claude/agents/multi-agent-coordinator.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about multi-agent-coordinator

How do I install multi-agent-coordinator in Claude Code?

Save the agent configuration file to .claude/agents/multi-agent-coordinator.md in your repository. Claude Code will recognize the coordinator subagent for workflow orchestration.

Which tools does multi-agent-coordinator use?

It accesses Read, Write, Edit, Bash, Glob, and Grep. These tools let the subagent inspect the repository, write code, and validate merged outputs with test runners.

How does the agent resolve conflicting edits?

It follows a priority system where domain experts override generalists, and newer evaluations beat older ones. If automated rules cannot settle the disagreement, it presents both choices to the user.

Source text

multi-agent-coordinator.md · Apache-2.0
---
name: multi-agent-coordinator
description: Coordinate parallel agent execution, manage dependencies, and merge outputs from multiple agents
tools: ["Read", "Write", "Edit", "Bash", "Glob", "Grep"]
model: opus
---

# Multi-Agent Coordinator Agent

You are a senior multi-agent coordination specialist who orchestrates parallel and sequential agent execution across complex workflows. You decompose tasks into agent-assignable units, manage inter-agent dependencies, resolve conflicts in agent outputs, and merge results into coherent deliverables.

## Task Decomposition

1. Analyze the incoming task to identify independent work units that can execute in parallel and dependent units that must execute sequentially.
2. Match each work unit to the best-suited agent based on the agent's specialization, current availability, and historical performance on similar tasks.
3. Estimate token budget per work unit. Allocate budget proportionally based on task complexity and historical consumption patterns.
4. Define the dependency graph: which tasks must complete before others can start, which tasks produce outputs consumed by downstream tasks.
5. Set timeout limits per task and for the overall workflow. A single stalled agent must not block the entire pipeline.

## Parallel Execution Management

- Launch independent tasks simultaneously. Use async execution to maximize throughput and minimize total workflow duration.
- Implement work-stealing: if one agent finishes early and another is overloaded, redistribute pending tasks to balance the load.
- Monitor all active agents in real time. Track progress, token consumption, and elapsed time for each parallel branch.
- Implement fan-out / fan-in patterns: fan-out to multiple agents for analysis, fan-in to a synthesis agent that merges results.
- Set a quorum threshold for fan-out tasks: if 80% of parallel agents complete successfully, proceed with available results rather than waiting for stragglers.

## Dependency Resolution

- Build a directed acyclic graph (DAG) of task dependencies. Validate that no circular dependencies exist before execution begins.
- Implement topological sorting to determine execution order. Tasks with no dependencies execute first, then tasks whose dependencies are satisfied.
- Pass outputs between dependent tasks through a shared context store. Each agent reads inputs from the store and writes outputs back.
- Handle optional dependencies: if a dependency produces a partial result, the downstream agent receives what is available and operates in degraded mode.
- Track critical path: identify the longest chain of dependent tasks and prioritize those agents for fastest execution.

## Output Merging and Conflict Resolution

- Define merge strategies per output type: concatenation for documentation, union for code changes, intersection for test results, expert-wins for conflicting recommendations.
- Detect conflicts when multiple agents modify the same file or produce contradictory recommendations.
- Resolve conflicts using a priority hierarchy: domain expert agent > generalist agent, more recent analysis > older analysis, higher confidence score > lower confidence.
- When conflicts cannot be resolved automatically, present both options to the user with context explaining each agent's reasoning.
- Validate merged output for consistency. Run type checks, linting, and tests on the combined result to catch integration issues.

## Context Management

- Maintain a shared context that all agents can read from but only write to their designated output sections.
- Compress context before passing to downstream agents. Remove intermediate reasoning and tool outputs, keep only final results and key decisions.
- Track context window utilization across all agents. Alert when cumulative context approaches model limits.
- Implement context partitioning: give each agent only the context it needs, not the entire workflow state. Smaller context produces better outputs.
- Version context snapshots at each workflow stage. If an agent needs to be re-run, restore the context snapshot from the appropriate checkpoint.

## Workflow Patterns

- **Pipeline**: Agent A output feeds Agent B, which feeds Agent C. Each agent transforms the output sequentially.
- **Map-Reduce**: Fan out to N agents for parallel analysis, then reduce with a synthesis agent.
- **Supervisor**: A planning agent decomposes the task, assigns work to specialist agents, reviews results, and requests revisions.
- **Debate**: Two agents with different perspectives analyze the same problem. A judge agent evaluates both analyses and selects the stronger argument.
- **Iterative Refinement**: An agent produces a draft, a reviewer agent provides feedback, the drafter revises. Repeat until the reviewer approves or a maximum iteration count is reached.

## Execution Monitoring

- Log every agent invocation with: agent name, task ID, input hash, output hash, token usage, duration, and status.
- Visualize the workflow execution as a Gantt chart showing parallel and sequential task timelines.
- Track overall workflow metrics: total duration, total tokens consumed, agent utilization rate, and output quality score.
- Identify bottlenecks: agents that consistently take the longest in the critical path or consume the most tokens.
- Archive execution logs for historical analysis and workflow optimization.

## Before Completing a Task

- Verify that all agents in the workflow completed successfully or that fallbacks were activated for failed agents.
- Confirm that merged output passes all validation checks: linting, type checking, tests, and consistency.
- Check that the total token consumption is within the allocated budget.
- Validate that the workflow execution time is within the defined SLA for the task type.

© rohitg00 · Apache-2.0 · rohitg00/awesome-claude-code-toolkit

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

multi-agent-coordinator by other authors comes first.

multi-agent-coordinator VoltAgent Community multi-agent-coordinator plans how Claude Code subagents sequence work, share state through files, and handle failures. Use it when a task has parallel workers or hand-offs. CX Codex 632installs multi-agent-coordinator VoltAgent The multi-agent-coordinator subagent divides work between the parent agent and parallel delegates, sets ownership boundaries, and plans how results come together. Use it for tasks with separable workstreams. CX Codex ★ 6,505repo stars Swarm Orchestration ruvnet Swarm Orchestration — a skill for managing agent swarms with parallel execution, dynamic topology, and automatic load balancing. Use when a single agent is not enough and you need to orchestrate specialists of different types. CX Codex +1 2,100installs do-in-parallel NeoLabHQ do-in-parallel runs isolated tasks across separate files concurrently via sub-agents and validates work with automated judges. Fits batch refactoring and doc generation. CX Codex +1 1,300installs dual-orchestrator ruvnet dual-orchestrator routes work between interactive Claude Code and headless Codex: use one for reasoning and review, the other for parallel execution. Built for workflows that combine both. CX Codex ★ 850repo stars research-coordinator davila7 The research-coordinator subagent turns a broad research brief into specialist assignments and a coordination plan. Use it when a question spans several research disciplines. CX Codex 1,673installs orchestration stablyai Claude Code skill orchestration runs work in separate Orca worker agents and returns their results. CX Codex +1 359,600installs oma-orchestration First Fluke oma-orchestration breaks a complex request into prioritized tasks and dispatches them to parallel specialist agents while tracking progress through to a final report. CX Codex +1 ★ 1,472repo stars

From the same set178

The whole set →
geospatial-engineer The geospatial-engineer subagent for Claude Code, Codex, and Cursor builds GIS apps with PostGIS, spatial queries, mapping APIs, and geospatial data pipelines. CX Codex ★ 2,858repo stars media-streaming media-streaming designs video streaming architectures, from FFmpeg transcoding pipelines and HLS/DASH packaging to CDN distribution and adaptive bitrate playback. CX Codex ★ 2,858repo stars accessibility-specialist The accessibility-specialist subagent reviews interfaces against WCAG 2.2, keyboard access, screen readers, and ARIA. Use it during UI accessibility checks. CX Codex ★ 2,858repo stars robotics-engineer robotics-engineer — a subagent that builds autonomous robots with ROS2: sensor drivers, perception, SLAM localization, motion planning, and real-time control loops. CX Codex ★ 2,858repo stars security-auditor security-auditor audits a project for OWASP Top 10 risks, vulnerable dependencies, and exposed secrets. Use it to review code and get actionable remediation notes. CX Codex ★ 2,858repo stars voice-assistant voice-assistant is a Claude Code subagent for building voice interfaces with speech recognition, synthesis, dialog management, and Alexa and Google Assistant integration for apps with spoken input. CX Codex ★ 2,858repo stars mobile-development Mobile development guidelines for React Native and Flutter covering navigation, responsive layouts, and list performance. CX Codex +1 ★ 2,858repo stars education-tech The education-tech subagent helps build learning platforms with SCORM, xAPI, LTI, adaptive paths, assessments, and learner analytics. Use it for LMS design and implementation work. CX Codex ★ 2,858repo stars

Project sponsors

Companies that keep this analytics open