orch-add-feature

affaan-m ｜ Agent 與工作流 ｜ 原文 ｜ MIT

統籌新增功能：研究、規劃、TDD、審查到有關卡的 commit

---
name: orch-add-feature
description: 統籌從頭到尾打造全新功能：研究、規劃、TDD 實作、審查、有關卡的 commit，每個階段都委派給對應的 ECC agent。要新增還不存在的能力時使用。
metadata:
  origin: ECC
---

# orch-add-feature

Actor · action · target：**orch · add · feature**。包在
[`orch-pipeline`](../orch-pipeline/SKILL.md) 共用引擎外面的薄包裝。

## When to Use

- 使用者想要一個**還不存在**的能力（「新增」「建立」
  「實作」「支援……」）。
- 這是全新的行為，不是修正（`orch-fix-defect`），也不是
  更改既有的行為（`orch-change-feature`）。

## Operation settings

- **預設的大小下限：** standard，除非明顯很小，否則要跑 Research + Plan。
- **階段遮罩：** 0 → 1 → 2 → 4 → 5 → 6（跳過 3 Scaffold；那只用於 MVP）。
- **第一步（階段 4）：** 針對新行為寫*新的*失敗測試，然後
  實作到全綠。

## How It Works

1. 用上面的設定執行 `orch-pipeline` 引擎。
2. 先分類大小；小的或瑣碎的功能會收斂成 4 → 5 → 6。
3. 停在 **Gate 1**（計畫核准）和 **Gate 2**（commit 前）。
4. 如果功能碰到安全觸發條件，就加上 `security-reviewer`。

> 相關：`/feature-dev` 是這個流程的獨立版本。`orch-add-feature`
> 的差別在於和家族其他成員共用 `orch-pipeline` 引擎，也就是大小分類器和
> 兩個關卡，所以能把瑣碎的功能縮到 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]
```

---
name: orch-add-feature
description: Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
metadata:
  origin: ECC
---

# orch-add-feature

Actor · action · target: **orch · add · feature**. Thin wrapper over the shared
engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).

## 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`).

## 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.

## How It Works

1. Run the `orch-pipeline` engine with the settings above.
2. Classify size first; small / trivial features collapse toward 4 → 5 → 6.
3. Stop at **Gate 1** (plan approval) and **Gate 2** (pre-commit).
4. 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.

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