What does this skill do?

The Plan Orchestrator Skill breaks down a plan document (PRD, RFC, or implementation plan) into individual steps and generates a copy-and-paste-ready /orchestrate custom command for each one, automatically chaining together agents from the ECC catalog based on the task type. It detects the installation mode (plugin or legacy), the project language, and condenses each description so that it is self-contained and verifiable.

Multi-step plans for commands
Convert a PRD or RFC with multiple steps into a chain of /orchestrate custom commands, without having to manually compose the agent strings.
Dry run to validate decomposition
Run in --dry-run mode to review the breakdown of steps and the justification for each string before generating the final commands.
Automatic Tagging by Task Type
Assign tags (design, impl, test, refactor, migration, db, security, etc.) and build the corresponding agent chain, deduplicating to a maximum of 4.
Batch processing
Generate a block containing all the commands in order so you can paste them all at once and execute the entire plan sequentially.

Usage examples

📋 Complete Plan
Implement this plan: @docs/plan/example-feature.md --lang=python
🔍 Validation dry run
Give me Orchestrate prompts for each step in @docs/plan/migration.md --lang=go --dry-run
🎯 With a limited scope
Build chains for this plan: @docs/plan/big-refactor.md --lang=auto --scope=steps-1-5
🏗️ Legacy Plan
Implement this plan in legacy mode: @docs/plan/legacy-feature.md --lang=typescript

Features

Automatic ECC Mode Detection Identifica si la instalación es plugin (/ecc:orchestrate con agentes ecc:<name>) o legacy (/orchestrate con agentes <name>) y usa una sola forma en toda la salida.
Project Language Detection With --lang=auto, it detects the predominant language using files such as pyproject.toml, package.json, go.mod, or Cargo.toml.
Flexible Breakdown of Steps Extracts steps from explicit numbering, "Step" columns in tables, blocks separated by ---, or H2 headings.
Autonomous Description Compression Each task includes a reference to the plan, 1–3 verifiable acceptance criteria, and, if specified in the plan, an “Out of Scope” clause.
String Self-Check Verify that all agents are in the ECC catalog, that there are no duplicates, that the chain is ≤4, and that the impl/refactor/migration steps end with a reviewer.

Frequently asked questions

No. The skill is purely generative: it produces commands that are ready to be pasted, but the user decides when to execute them.
Usa el catálogo ECC. Detecta automáticamente si tu instalación es modo plugin (agentes ecc:<name>) o legacy (agentes <name>) y nunca mezcla ambas formas.
For plans with more than 1,500 lines, it enters summary-only mode: it outputs only the summary table and prompts you to narrow the scope with --scope before running again.
Yes. With --lang=auto, it detects the predominant language; if it cannot determine it, it sets it to "unknown" and uses the default string "code-reviewer."
Plan Orchestrator — Automatic chaining of agents with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.