Agent skill · creative production · affaan-m
plan-orchestrate
Read a plan document, decompose it into steps, classify each step, and emit the ready-to-paste ECC slash command for that step, carrying the step identifier and scope in the command's own documented argument form. Generative only — never invokes commands itself and never claims to control what a command runs internally. Steps whose command cannot carry plan scope fail closed instead of being emitted. Use when the user has a multi-step plan and wants the right command for each step without picking it by hand.
Why this skill is useful
Generates specific orchestrate commands for multi-step plans that the AI wouldn't reliably create on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Plan Orchestrate Bridge a plan document to the current ECC slash-command surface by emitting one ready-to-paste command per step. This skill is a router only: it picks the command and fills in the command's own documented argument form. It does not compose agent chains and does not influence what a command runs internally — each command owns its own execution behavior. The skill is generative only; it never executes commands. The user pastes each line when ready. When to Use User has a multi-step plan document (PRD, RFC, implementation plan) and wants ready-to-paste commands for each step. User says "turn this plan into commands", "what command should I run for each step", "orchestrate this plan". A step-by-step plan exists but the user does not want to manually pick a command per step. Skip when: The work is one ad-hoc step → run the appropriate slash command directly (see the catalogue below). The plan is unreadable or empty. Lack of explicit numbering alone is not a skip condition — see the "No clear steps" edge case below. The plan should run autonomously in the background → prefer dmux-workflows or the native workflows/.workflow.js scripts instead. Inputs <plan-doc-path> — required; relative or absolute path (@docs/... accepted). --scope — limits emitted steps; defaults to all. --dry-run — print decomposition + command rationale only; do not emit final commands. Scope rule — a step is only emitted if the command can carry it Every emitted command must carry its step's identity and scope. A command accepts arguments only in the form its own file documents (frontmatter argument-hint or a ## Usage section; docs/COMMAND-REGISTRY.json is the generated index). The only form that carries a plan step is a free-form task-description argument, because that argument travels with the command when it is pasted. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/plan-orchestrate--2745cc