Orchestrated Feature Development
Build a brand-new feature end to end with Muse through the shared orch-pipeline engine: research, plan, TDD implementation, review, and gated commit, with plan approval and pre-commit gates.
- What
- Build a brand-new feature end to end with Muse through the shared orch-pipeline engine: research, plan, TDD implementation, review, and gated commit, with plan approval and pre-commit gates.
- Cost
- Free
- Needs
- Use "Orchestrated Feature Development" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a thin, disciplined wrapper over the shared orch-pipeline engine for the most common orchestration request, adding a capability that does not exist yet. The flow runs the engine with tuned settings: standard size floor (run Research plus Plan unless clearly small), phase mask 0, 1, 2, 4, 5, 6 (Scaffold is MVP-only), and the first move in phase 4 is writing new failing tests for the new behavior before implementing to green. Two hard gates structure the work: Gate 1 requires plan approval before any code, Gate 2 requires confirmation before commit. If the feature touches a security trigger, a security-reviewer is added automatically. The size classifier right-sizes the flow: small or trivial features collapse toward phases 4, 5, 6 instead of running the full ceremony. It differs from the standalone /feature-dev flow by sharing the engine, the size classifier, and both gates with the rest of the orch family, so behavior stays consistent across feature adds, changes, and MVP builds. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this is for net-new behavior only; corrections go to orch-fix-defect and alterations of existing behavior to orch-change-feature. The gates need a human at the keyboard; do not auto-approve them away. The shared engine means the skill's value depends on the orch-pipeline setup in your harness. 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 "Orchestrated Feature Development" with your Muse. Prerequisites: none to install. Pure guidance; works best with the orch-pipeline engine and ECC agents available in your harness. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/orch-add-feature/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Add [feature] to [project]" or "Build OAuth2 login for [app] end to end." 3. Work through the phases with Muse: research, plan (Gate 1: approve before code), TDD implementation, review, gated commit (Gate 2: confirm). Tip: for clearly small features, let the size classifier collapse the flow to phases 4, 5, 6 instead of running the full ceremony. Safety: a skill is plain-text instructions; it runs nothing by itself. The gates need a human decision; never auto-approve 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.