back
loading skill details...
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.…
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 custom directly. 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]
don't have the plugin yet? install it then click "run inline in claude" again.