Plan Orchestrate
Turn plan documents into agent chains for Muse: decomposes each step, picks the right ECC agents, emits ready-to-paste orchestration commands. Generative only.
- What
- Turn plan documents into agent chains for Muse: decomposes each step, picks the right ECC agents, emits ready-to-paste orchestration commands. Generative only.
- Cost
- Free
- Needs
- Use "Plan Orchestrate" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a bridge from a plan document to driven multi-agent execution, so Muse turns your PRD or RFC into ready-to-paste orchestration commands instead of you composing agent chains by hand. Generative only, it never invokes /orchestrate itself, you paste each line when ready. Works in five phases: detect the ECC install form (plugin versus legacy, so command and agent prefixes stay in sync) and the project language (polyglot-aware, with a PyTorch sub-profile) ; decompose the plan into step units from numbering, tables or headings ; tag each step by intent (design, plan, impl, test, refactor, migration, db, security, build, docs, lookup, review, loop) and compose a chain of up to four agents from the ECC catalogue with composition rules (security-sensitive impl ends with security-reviewer, db work gates through database-reviewer, impl steps end with a reviewer) ; compress each step into a self-contained one-line task description with acceptance criteria and inherited scope guards ; then emit Markdown with an overview table, per-step bash blocks, and a batch execution block, followed by a self-check (catalogue names only, uniform prefix form, no invented flags). Handles edge cases: no clear steps, large plans (overview-only mode), over-broad steps, plan-declared agents, polyglot ties. Use when you have a multi-step plan and want to drive it through orchestration without hand-composing chains. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: generative only, it never executes anything itself ; requires the ECC agent catalogue installed (plugin or legacy form) for the emitted commands to resolve ; chain quality follows plan quality, garbage plans yield garbage chains. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Plan Orchestrate" with your Muse. Prerequisites: none to install for the skill itself. The emitted commands need the ECC agent catalogue installed (plugin or legacy form) to resolve. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/plan-orchestrate/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Orchestrate this plan: [paste the plan document path or its text]." 3. Review the emitted per-step commands, then paste each orchestrate line into Claude Code when ready. The skill never executes anything itself. Tip: use --dry-run style ("decompose only, no final prompts") to sanity-check the step breakdown before committing. Safety: a skill is plain-text instructions; it runs nothing by itself. Review each emitted command before pasting.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.