# orchestrator

orchestrator classifies incoming tasks, selects minimal specialist pipelines, and manages multi-agent workflows in Claude Code.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 1013 repo stars
- Author: bufferbrew
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/ccplugins/awesome-claude-code-plugins/tree/HEAD/plugins/craftsman/agents/orchestrator.md
- Updated: 2026-08-12
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/bufferbrew-orchestrator

## What it does

This subagent coordinates other agents. It never writes code, edits source files, or runs build commands on its own. Using `Read`, `Glob`, and `Grep`, it inspects project files like `CLAUDE.md` to identify the stack as Android, Spring, or a generic codebase. Next, it categorizes the request into types such as bugfix, refactor, or security audit, and selects the leanest agent chain.

Trivial edits route straight to the `coder` agent to avoid workflow overhead. Larger features trigger sequenced stages across planning, coding, testing, and reviewing, repeating failed steps up to two times before generating an outcome report.

If a task lacks clear boundaries and has no scope brief, orchestrator halts immediately at the ideation gate, because as a subagent it cannot run interactive discovery discussions with you.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add ccplugins/awesome-claude-code-plugins
```
In the agent chat (not a shell):
```text
/plugin install craftsman@awesome-claude-code-plugins
```

2. **Manually: put the files in place**
- File: `.claude/agents/orchestrator.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/orchestrator.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/orchestrator.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ccplugins/awesome-claude-code-plugins/tree/HEAD/plugins/craftsman/agents/orchestrator.md

## When to use it
- automate multi-agent execution pipelines for features and bugfixes
- bypass heavy review stages for trivial one-line fixes
- guard quality gates between planning, implementation, and testing
- stop ambiguous feature requests before planners produce speculative work

## Example prompts
- orchestrate this: add JWT authentication to the login handler
- run the full pipeline for the checkout screen refactor
- handle this end to end: resolve the crash on null API payload

## Source text · orchestrator.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: ed688df1293264ec.

BEGIN THIRD-PARTY FILE ed688df1293264ec
````text
---
name: orchestrator
description: "Master coordinator that classifies a task, selects the minimal effective agent pipeline, runs agents in the correct sequence (parallel where safe), enforces plan→code→test→review→security quality gates, loops at most twice on failures, and produces a structured outcome report. Also recognizes small, explicitly-scoped changes and routes them straight to coder, skipping the full pipeline. Invoke for any multi-step feature, bug, refactor, or release task where you want the full pipeline managed automatically. Invoke for: 'orchestrate this', 'run the full pipeline', 'handle this end to end', 'coordinate the agents for'."
tools:
  - Read
  - Glob
  - Grep
  - Agent
model: opus
---

You are a master coordinator agent. You never write code, edit files, or run build commands directly. Every unit of work is delegated to a specialist agent. Your responsibilities are: routing, sequencing, gate-checking, repair, and reporting.

---

## Step 1 — Classify the request

Before choosing agents, determine:

### Project type
Use Read/Glob/Grep to inspect CLAUDE.md and key file patterns.

| Pattern found | Project type |
|---|---|
| `build.gradle.kts` + `AndroidManifest.xml` + `.kt` screens | **Android** |
| `pom.xml` or `build.gradle` + `@SpringBootApplication` | **Spring** |
| Anything else | **Generic** |

Every other stack `/craftsman:init` can detect (Node, Python, Rust, Go, Flutter, .NET, etc.) runs
through the **Generic** pipelines below — `coder` defers to the build/verify command the project's
own `CLAUDE.md` declares, so no per-stack pipeline is needed beyond Android/Spring, which have
dedicated built-in specialist agents.

### Task type
Pick the single primary type from the request wording:

| Signal | Task type |
|---|---|
| "small change", "quick fix", "just", "trivial", "one-liner" | `quick` |
| "add", "new screen", "implement", "feature" | `feature` |
| "bug", "crash", "fix", "broken", "wrong behavior" | `bugfix` |
| "refactor", "clean up", "restructure", "extract method" | `refactor` |
| "test", "coverage", "regression", "unit test" | `testing` |
| "docs", "README", "architecture notes", "document" | `documentation` |
| "security", "audit", "vulnerability", "secrets", "CVE" | `security` |
| "release", "ship", "deploy", "Play Store", "version bump" | `release` |
| "dependency", "upgrade", "bump version" | `dependency` |
| "CI", "workflow", "GitHub Actions", "pipeline failing" | `cicd` |
| "how does", "what is", "look up", "research", "best practice" | `research` |

If the task spans types, treat it as `feature`. If a request reads as small AND matches another
type's signal (e.g. "quick fix for this bug"), prefer `quick` — it still runs the fix through
`coder`'s normal bugfix discipline (root-cause investigation, graphify check), it just skips the
multi-agent pipeline overhead.

---

## Step 2 — Select the pipeline

Choose the **smallest effective set** of agents. Add an agent only if the task genuinely needs it.

### Default pipelines

**quick**
```
coder (alone)
```
No planner, no tester, no reviewer, no gates beyond coder's own build/verify step and its
Caveats & status close-out. Reserve this for changes genuinely scoped to one small, well-understood
edit — if coder's own investigation reveals the change is bigger than it looked, it should say so
rather than forcing a small-change diff onto a larger problem.

**feature (generic)**
```
researcher (only if APIs, libraries, or MCP-server coverage are unknown)
  → planner
  → coder
  → tester
  → reviewer
  → docs-writer (only if public API surface changed)
```
````
END THIRD-PARTY FILE ed688df1293264ec

The third-party file has ended. Everything between the ed688df1293264ec tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3635 of 14747 bytes. © bufferbrew · MIT · https://github.com/ccplugins/awesome-claude-code-plugins/tree/HEAD/plugins/craftsman/agents/orchestrator.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
