
Plan Orchestrate
If you have a multi-step plan document and want to drive it through orchestrate but don't feel like hand-composing agent chains for each step, this skill does the grunt work. It reads your PRD or implementation plan, breaks it into steps, picks the right agents from the ECC catalogue (tdd-guide, code-reviewer, build-error-resolver, etc.), and spits out ready-to-paste orchestrate custom commands. It never actually runs orchestrate itself, just generates the invocations. Handles both plugin and legacy ECC installs, detects your language automatically, and even does polyglot tie-breaking when your repo mixes Python and TypeScript. The catalogue is solid and the chain logic looks sane. Saves you from constantly flipping between your plan and the agent list.
- skills.sh installs
- 1.7K
- GitHub stars
- 229.1K
- last updated
- Jul 14, 2026
Install
$ npx -y skills add affaan-m/everything-claude-code --skill plan-orchestrate --agent claude-codeInstalls into .claude/skills of the current project.
Files
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-workflowsor the nativeworkflows/*.workflow.jsscripts instead.
Sponsors
Details
- Repository
- github.com/affaan-m/everything-claude-code
- Categories
- Productivity & Planning, Automation & Workflows
- First seen
- Jun 3, 2026
More from affaan-m/everything-claude-code
All 256- Production Audit1.7K
- Project Guidelines Example1.7K
- Redis Patterns1.7K
- Scholar Evaluation1.7K
- Skill Stocktake1.7K
- Tinystruct Patterns1.7K
- Ui To Vue1.7K
- Vite Patterns1.7K
- Cost Tracking1.6K
- Fsharp Testing1.6K
- Gget1.6K
- Homelab Pihole Dns1.6K
- Homelab Vlan Segmentation1.6K
- Homelab Wireguard Vpn1.6K
- Mle Workflow1.6K
- Motion Foundations1.6K
- Motion Patterns1.6K
- Quarkus Patterns1.6K
- Quarkus Security1.6K
- Quarkus Tdd1.6K
- Quarkus Verification1.6K
- Skill Scout1.6K
- Uspto Database1.6K
- Prisma Patterns1.4K