/orch-change-feature
Orchestrate altering an existing, working feature to new desired behavior — update tests to the new spec, change impl, review, gated commit. Wrapper for the orch-change-feature skill.
> /plugin marketplace add affaan-m/ECC > /plugin install ecc@ecc
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/orch-change-feature
Context preview
What this command does when you run it.
Orchestrate altering an existing, working feature to new desired behavior — update tests to the new spec, change impl, review, gated commit. Wrapper for the orch-change-feature skill.
Command definition
orch-change-feature.mddescription: Orchestrate altering an existing, working feature to new desired behavior — update tests to the new spec, change impl, review, gated commit. Wrapper for the orch-change-feature skill.
/orch-change-feature
Manually launch the **orch-change-feature** orchestrator: change behavior that already works to a new desired spec, tests-first.
Usage
/orch-change-feature <the new desired behavior>
Examples:
/orch-change-feature make nws-poller alert at 2 warnings instead of 3 /orch-change-feature instead of sorting by date, sort by priority
What It Does
Invoke the `orch-change-feature` skill with `$ARGUMENTS` as the request. The skill (via the shared `orch-pipeline` engine) will:
1. Classify size (default floor: small) and state the tier. 2. Light plan only if the new behavior needs research. → **GATE 1** (approve changed-test plan). 3. **Update the existing tests** to express the new behavior, then change the implementation until green. (Changing the tests first is what makes this a tweak, not a fix.) 4. `code-reviewer` (+ `security-reviewer` on a security trigger), then commit. → **GATE 2**.
Use this only when the feature **works** but should behave differently — not for bugs (`/orch-fix-defect`) or net-new capability (`/orch-add-feature`).
If `$ARGUMENTS` is empty, ask the user what behavior should change.
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Repo: affaan-m/ECC
Other commands on ecc.
- /add-language-rules
Workflow command scaffold for add-language-rules in everything-claude-code.
Open command - /database-migration
Workflow command scaffold for database-migration in everything-claude-code.
Open command - /feature-development
Workflow command scaffold for feature-development in everything-claude-code.
Open command - /aside
Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.
Open command - /auto-update
Pull the latest ECC repo changes and reinstall the current managed targets.
Open command - /build-fix
Detect the project build system and incrementally fix build/type errors with minimal safe changes.
Open command