Back to Details

orch-change-feature

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

orch-change-feature

orch-change-feature

Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in 
orch-pipeline
.
角色·操作·目标：orch · change · feature。这是对
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).
  • 现有功能正常运行，但需要调整为新的预期行为（如“修改”、“调整”、“新增XX功能”、“将X替换为Y”）。
  • 需与同类技能区分：
    • 功能未损坏 → 不使用
      orch-fix-defect
      （无需要复现的bug）。
    • 功能非新增 → 不使用
      orch-add-feature
      （该功能能力已存在）。

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.
  • 默认最小规模：小型 —— 大多数调整仅涉及一两个函数。
  • 阶段掩码：0 →（若新行为需要调研则设为1）→ 轻度2 → 4 → 5 → 6。
  • 第一步（阶段4）：更新现有测试用例以表达新的预期行为，然后修改实现代码直至测试通过。先修改测试用例是区分“调整”与“修复”的关键。

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.
  1. 使用上述设置运行
    orch-pipeline
    引擎。
  2. 保持计划轻量化 —— 只有
    standard
    及以上规模才需要完整的
    planner
    流程。
  3. 在**Gate 1（计划/修改后测试用例审批）和Gate 2（预提交）**处暂停。
  4. 若修改涉及安全触发点，需添加
    security-reviewer
    。

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]
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]