Agent skill · software engineering · affaan-m
orch-change-feature
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Why this skill is useful
Adds a specific orchestration workflow for changing feature behavior that includes updating tests and implementation, which the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
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. How It Works 1. Run the orch-pipeline engine with the settings above. 2. Keep the plan light — only standard+ size warrants the full planner pass. 3. Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit). 4. Add security-reviewer if the change touches a security trigger. Example
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/orch-change-feature