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.
- License 许可
- MIT
- 最近更新
- 2026-11-05
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- orch-change-feature
- metadata
- { "origin": "ECC" }
- description
- 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.
03 SKILL.md 正文
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).
- 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]
04 同仓库更多 Skills
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
windows-desktop-e2e
E2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.