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.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Orch Change Feature when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Orch Change Feature when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/orch-change-feature # Save SKILL.md to ~/.claude/skills/orch-change-feature/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/orch-change-feature/SKILL.md. For a shared project, commit the folder at .claude/skills/orch-change-feature/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Orch Change Feature skill for this task: An existing feature works, but the desired behavior is different ("change",. Confirm any required inputs or files before making changes.What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# orch-change-feature
Actor · action · target: **orch · change · feature**. Thin wrapper over the shared engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
## 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
``` 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] ```
Intended uses
- An existing feature works, but the desired behavior is different ("change",
- Distinguish from siblings:
- not broken → not orch-fix-defect (no bug to reproduce).
- not new → not orch-add-feature (the capability already exists).
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.