SKILL

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.

适用对象：对象待分类。自动收录 · 待核查。

原作者说明节选

从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。

查看英文原文

原文涵盖的主题

orch-change-feature
When to Use
Operation settings
How It Works
Example

Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in orch-pipeline. 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). 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. 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.

来源仓库: affaan-m/ECC
源文件: skills/orch-change-feature/SKILL.md
固定版本: d2ef2680594f9a17526a6e1a2e18b3d242c5d17b

阅读完整原作者说明 ↗