orch-add-feature

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

orch-add-feature

Actor · action · target: orch · add · feature. Thin wrapper over the shared engine in

orch-pipeline

角色·操作·目标：orch · add · feature。是对

orch-pipeline

中共享引擎的轻量封装。

When to Use

使用场景

The user wants a capability that does not exist yet ("add", "build", "implement", "support …").
It is net-new behavior — not a correction (
```
orch-fix-defect
```
) and not an alteration of existing behavior (
```
orch-change-feature
```
).

用户需要当前不存在的功能（如“添加”“构建”“实现”“支持……”）。
属于全新行为——不是缺陷修复（
```
orch-fix-defect
```
），也不是对现有行为的修改（
```
orch-change-feature
```
）。

Operation settings

操作设置

Default size floor: standard — run Research + Plan unless clearly small.
Phase mask: 0 → 1 → 2 → 4 → 5 → 6 (skip 3 Scaffold; that is MVP-only).
First move (phase 4): write new failing tests for the new behavior, then implement to green.

**默认规模下限：**标准——除非明确是小型功能，否则运行调研+规划阶段。
**阶段掩码：**0 → 1 → 2 → 4 → 5 → 6（跳过第3阶段“搭建框架”；该阶段仅适用于MVP）。
**第一步（第4阶段）：**为新行为编写新的失败测试用例，然后实现代码使测试通过。

How It Works

工作原理

Run the
```
orch-pipeline
```
engine with the settings above.
Classify size first; small / trivial features collapse toward 4 → 5 → 6.
Stop at Gate 1 (plan approval) and Gate 2 (pre-commit).
Add
```
security-reviewer
```
if the feature touches a security trigger.

Related:
/feature-dev
is a standalone version of this flow.
orch-add-feature
differs by sharing the
orch-pipeline
engine — the size classifier and the two gates — with the rest of the family, so it right-sizes trivial features to 4 → 5 → 6.

使用上述设置运行
```
orch-pipeline
```
引擎。
首先对功能规模进行分类；小型/微型功能会简化为4 → 5 → 6阶段。
在**Gate 1（规划审批）和Gate 2（提交前检查）**处暂停。
如果功能涉及安全触发点，则添加
```
security-reviewer
```
。

相关内容：
/feature-dev
是此流程的独立版本。
orch-add-feature
的不同之处在于它与同系列工具共享
orch-pipeline
引擎——包括规模分类器和两个Gate——因此可以将微型功能合理简化为4 → 5 → 6阶段。

Example

示例

orch-add-feature: add OAuth2 login to nws-poller
→ research existing auth libs → plan task_list  [GATE 1: approve]
→ TDD each task → code-review (+ security-reviewer: auth path)
→ commit  [GATE 2: confirm]

orch-add-feature: add OAuth2 login to nws-poller
→ research existing auth libs → plan task_list  [GATE 1: approve]
→ TDD each task → code-review (+ security-reviewer: auth path)
→ commit  [GATE 2: confirm]