plan-orchestrate

Topics in the source

• Plan Orchestrate
• When to Use
• Inputs
• Scope rule — a step is only emitted if the command can carry it
• Task description (scope-carrying commands only)
• Command catalogue
• How It Works
• Phase 0 — Read the plan

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. 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. — required; relative or absolute path (@docs/... accepted

This is an excerpt. Refer to the complete source and its current requirements.