plan-orchestrate
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.
npx skills add mturac/everything-openai-codex --skill plan-orchestrate --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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] ``` - `<plan-doc-path>` — required; relative or absolute path (`@docs/...` accepted). - `--lang` — reviewer language variant; defaults to `auto` (detected from project). - `--scope` — limits emitted steps; defaults to `all`. - `--dry-run` — print decomposition + chain rationale
- When to Activate
- Inputs
- Authoritative /orchestrate shape (do not deviate)
- ecc install form and namespacing
- Available agent catalogue (must pick from these)
- How It Works
- Phase 0 — Detect ecc mode + language
- Phase 1 — Decompose steps
- Phase 2 — Tag and pick chain
- Phase 3 — Compress task description
- Phase 4 — Output
- Phase 5 — Self-check (run before emitting)
- Edge cases
- Examples
What does the plan-orchestrate skill do?
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.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill plan-orchestrate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.