orch-change-feature
SkillDev toolsorch-change-feature is a skill for changing how an existing, working feature behaves. It guides an agent through updating the feature's tests to the new spec, changing the implementation to match, reviewing the code, and committing. It is meant for cases where behavior is not broken but should be different.
Use orch-change-feature in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add orch-change-feature and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the orch-change-feature skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an existing feature that works but needs to behave differently.
What your AI can do with it
- Update existing tests to the new spec before changing implementation
- Change the implementation until the updated tests pass
- Run a code review of the change
- Pause for approval at the plan stage and before committing
- Add a security review when the change touches security-sensitive code
- Commit the change after approval
Getting started
- Have an existing feature that works but needs to behave differently.
- Add the orch-change-feature skill to your agent setup.
- Describe the new desired behavior to the agent.
- Approve the plan when the agent pauses for your review.
- Approve the commit when the agent pauses before committing.
What this skill tells your AI
The instructions your AI receives, as published by affaan-m/ecc in skills/orch-change-feature/SKILL.md and read by ahel’s review.
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).
- not broken → not
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.
How It Works
- Run the
orch-pipelineengine with the settings above. - Keep the plan light — only
standard+ size warrants the fullplannerpass. - Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
- Add
security-reviewerif the change touches a security trigger.
Example
orch-change-feature: make nws-poller alert at 2 warnings instead of 3
→ update threshold tests to new spec → change impl to green
→ code-review → commit [GATE 2: confirm]
Signals
- GitHub stars
- 270k
- Forks
- 40k
- Last commit
- Sep 2026
Questions
- When should I use this skill?
- Use it when behavior is not broken but should be different. It is for altering an existing, working feature to new desired behavior.
- Does it update tests first?
- Yes. It updates the existing tests to the new spec, then changes the implementation to match.
- Does it commit automatically?
- No. It pauses for your approval before committing.
- Does it handle security-sensitive changes?
- It adds a security review when the change touches security-sensitive code.
- What happens if I do not approve the plan?
- The skill pauses for your approval at the plan stage, so you can review and decide before it proceeds.
Advanced
- Item type
- skill
- Key
orch-change-feature- Source
- github.com/affaan-m/ecc