Orch Change Feature

When you need to change how something already works rather than fix a bug or add something new, this orchestrates the full cycle: update tests to match the new spec first, then modify the implementation until green, review, and gated commit. It's a thin wrapper over orch-pipeline tuned for behavioral tweaks. The key insight is starting with test changes, which distinguishes "make it work differently" from "make it work correctly." Defaults to small scope since most feature adjustments touch just a function or two. Stops at two gates for approval, keeps planning light unless the change is large, and adds security review when needed. Straightforward workflow automation for the common case of "instead of X, do Y."

skills.sh installs: 4.8K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill orch-change-feature --agent claude-code

Installs into .claude/skills of the current project.

Files

orch-change-feature

Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in orch-pipeline.

When to Use

An existing feature works, but the desired behavior is different ("change", "adjust", "make it also …", "instead of X do Y").
Distinguish from siblings:
- not broken → not orch-fix-defect (no bug to reproduce).
- not new → not orch-add-feature (the capability already exists).

Operation settings

Default size floor: small — most tweaks are a function or two.
Phase mask: 0 → (1 only if the new behavior needs research) → light 2 → 4 → 5 → 6.
First move (phase 4): update the existing tests to express the new desired behavior, then change the implementation until they pass. Changing the tests first is what separates a tweak from a fix.