Orchestrated Feature Change
Change a working feature to new behavior with Muse: update tests to the new spec first, change the implementation until they pass, review, and gated commit.
- What
- Change a working feature to new behavior with Muse: update tests to the new spec first, change the implementation until they pass, review, and gated commit.
- Cost
- Free
- Needs
- Use "Orchestrated Feature Change" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an orchestration recipe that makes Muse change an existing, working feature to new desired behavior without turning the tweak into a regression. The key move is updating the existing tests to express the new desired behavior first, then changing the implementation until they pass; changing the tests first is what separates a tweak from a fix. The skill distinguishes the case from its siblings: not broken, so no bug reproduction ritual; not new, so no greenfield scaffolding, the capability already exists. The plan stays light, with the full planner pass reserved for standard-size changes and up, and research only when the new behavior needs it. Two gates keep humans in charge: Gate 1 approves the plan and the changed tests, Gate 2 confirms before the commit; a security reviewer joins if the change touches a security trigger. The skill is a thin wrapper over the shared orch-pipeline engine. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it is designed for the ECC harness, you need the orch-pipeline engine alongside; it assumes tests exist to update, without them the tests-first move has nothing to stand on. 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 Change" with your Muse. Prerequisites: none to install. Pure guidance; an existing feature with tests plus the ECC orch-pipeline engine helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/orch-change-feature/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Change this feature to the new behavior: [describe current behavior and desired behavior]. Update the tests to the new spec first." 3. Review the changed tests at Gate 1, review the implementation, and confirm at Gate 2 before the commit. Tip: say "this is a tweak, not a fix" so it skips the bug reproduction ritual. Safety: a skill is plain-text instructions; it runs nothing by itself. Never approve a gate you have not read.
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.