
About
Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without com
name: plan-orchestrate description: Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand. origin: ECC
Plan Orchestrate
Bridge a plan document to /orchestrate custom by emitting one ready-to-paste invocation per step. The skill is generative only — it never executes /orchestrate. The user pastes each line when ready.
When to Activate
- User has a multi-step plan document (PRD, RFC, implementation plan) and wants to drive it through
/orchestrate. - User says "orchestrate this plan", "give me orchestrate prompts for each step", "compose chains for this plan".
- A step-by-step plan exists but the user does not want to manually pick agents per step.
Skip when:
- The work is one ad-hoc step → call
/orchestrate customdirectly. - The plan is unreadable or empty. Lack of explicit numbering alone is not a skip condition — see the "No clear steps" edge case below.
Inputs
<plan-doc-path> [--lang=python|typescript|go|rust|cpp|java|kotlin|flutter|auto] [--scope=all|step:<n>|range:<a>-<b>] [--dry-run]
<plan-doc-path>— required; relative or absolute path (@docs/...accepted).--lang— reviewer language variant; defaults toauto(detected from project).--scope— limits emitted steps; defaults toall.--dry-run— print decomposition + chain rationale only; do not emit final prompts.
Authoritative /orchestrate shape (do not deviate)
{ORCH_CMD} custom "<agent1>,<agent2>,...,<agentN>" "<task description>"
Where {ORCH_CMD} is determined in Phase 0 (see below). The command string in the emitted output always uses one concrete form — never both, never a placeholder.
customis a sequential chain; each agent's HANDOFF feeds the next.- Comma-separated agent list. No spaces preferred; one space tolerated.
- No
--mode/--gate/--agents=...flags exist — never invent them. - Agent names come from the catalogue in this skill. Embedded double quotes in the task description are escaped as
\".
ECC install form and namespacing
Two install forms determine the prefix on both the slash command and every agent name. The two MUST stay in sync — one form per output, never mixed:
Let <claude-home> denote the Claude Code home directory: ~/.claude on macOS/Linux, %USERPROFILE%\.claude on Windows. Resolve it the way the host platform resolves the user home directory (do not hardcode ~).
| Form | Detection | {ORCH_CMD} | Agent name format |
|---|---|---|---|
| Plugin install (1.9.0+) | <claude-home>/plugins/marketplaces/everything-claude-code/ exists | /everything-claude-code:orchestrate | everything-claude-code:<name> |
| Legacy bare install | Above absent; agent files under <claude-home>/agents/ | /orchestrate | <name> |
Why this matters: under the plugin install, agents register as everything-claude-code:tdd-guide. Bare names force fuzzy matching, which fails intermittently under parallel calls. Under legacy, the prefixed forms are not registered and fail outright.
Available agent catalogue (must pick from these)
General:
planner— requirement restatement, risk decomposition, step planningarchitect— architecture, system design, refactor proposalstdd-guide— write tests → implement → 80%+ coveragecode-reviewer— generic code reviewsecurity-reviewer— security audit, OWASP, secret leakagerefactor-cleaner— dead code, duplicates, knip-class cleanupdoc-updater— documentation, codemap, READMEdocs-lookup— third-party library API lookups (Context7)e2e-runner— end-to-end test orchestrationdatabase-reviewer— PostgreSQL schema, migration, performanceharness-optimizer— local agent harness configurationloop-operator— long-running autonomous loopschief-of-staff— multi-channel triage (rarely a fit for plan steps)
Build error resolvers:
build-error-resolver(generic) /cpp-build-resolver/go-build-resolver/java-build-resolver/kotlin-build-resolver/rust-build-resolver/pytorch-build-resolver
Code reviewers:
python-reviewer/typescript-reviewer/go-reviewer/rust-reviewer/cpp-reviewer/java-reviewer/kotlin-reviewer/flutter-reviewer
A misspelled agent name fails /orchestrate. Cross-check against this list before emitting.
How It Works
Phase 0 — Detect ECC mode + language
- Read
<plan-doc-path>. If missing or empty, report and stop. - Detect ECC install form once and freeze it into
ECC_MODE. Algorithm (run in order, stop at the first match):- If
<claude-home>/plugins/marketplaces/everything-claude-code/exists →ECC_MODE=plugin. - Else if
<claude-home>/agents/exists and contains at least one ECC agent fil
- If
