Orchestrator Pipeline
The shared gated pipeline behind the orch-* family: Research-Plan-TDD-Review-Commit with size classification and two human gates.
- What
- The shared gated pipeline behind the orch-* family: Research-Plan-TDD-Review-Commit with size classification and two human gates.
- Cost
- Free
- Needs
- Use the orch-* operation skills with your Muse; "Orchestrator Pipeline" is their shared engine, not a standalone skill.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: the shared orchestration engine behind the orch-* skill family (orch-add-feature, orch-change-feature, orch-fix-defect, orch-refine-code, orch-build-mvp, all already listed here). The orch-* skills are thin wrappers; they do not re-implement any work. They classify the request, choose which phases of this pipeline run, and delegate each phase to an existing ECC agent or command. This file is that pipeline: a gated Research, Plan, TDD implementation, Review, and Commit sequence, with a size classifier that scales ceremony to blast radius (trivial, small, standard, large), an agent and command map per phase, a security-review trigger for sensitive diffs, and two human gates: plan approval before any implementation code, and commit confirmation before any commit. Everything between the gates flows without stopping. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this is a shared reference engine, not a standalone skill. Invoke an operation skill (orch-add-feature, orch-fix-defect, and the others) rather than this engine directly; read this file directly only when adding a new operation to the family or tuning the shared phases, gates, or agent map. 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 the orch-* operation skills with your Muse; "Orchestrator Pipeline" is their shared engine, not a standalone skill. 1. Pick the operation skill you need (all listed here): orch-add-feature for a brand-new feature, orch-change-feature for an existing behavior to change, orch-fix-defect for a broken behavior, orch-refine-code for a behavior-preserving refactor, orch-build-mvp for bootstrapping from a spec. 2. Open the engine reference only if you are adding a new operation or tuning shared phases: https://github.com/affaan-m/ECC/blob/main/skills/orch-pipeline/SKILL.md 3. Expect the two gates: approve the plan before implementation code is written, and confirm the commit before anything is committed. Tip: state the size tier (trivial, small, standard, large) up front; ceremony scales to blast radius and you can always override it. Safety: a skill is plain-text instructions; it runs nothing by itself. The gates are the safety; never let an agent skip Gate 1 or Gate 2.
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.