orch-build-mvp
統籌從設計或規格文件起步 MVP，用垂直切片搭配 GAN 建置迴圈
中文翻譯
---
name: orch-build-mvp
description: 統籌從設計或規格文件起步一個可運作的 MVP：讀入 SDD/PRD、規劃薄的垂直切片、搭出第一個端到端切片的骨架，再以 generator-evaluator 的建置迴圈推進，搭配審查和有關卡的 feat commit。設計或規格文件必須透過規劃好的垂直切片變成跑得起來的 MVP 時使用。
metadata:
origin: ECC
---
# orch-build-mvp
Actor · action · target：**orch · build · mvp**。包在
[`orch-pipeline`](../orch-pipeline/SKILL.md) 共用引擎外面的薄包裝。
## When to Use
- 使用者有一份**設計 / 規格文件**（SDD、PRD、system_design），想從它
起步一個可運作的垂直切片。
- 以文件路徑當參數，例如 `civicpulse/docs/SDD-v0.6.md`。
## Operation settings
- **預設的大小下限：** large，這是包含 Scaffold 的完整 pipeline。
- **階段遮罩：** 0（讀規格）→ 1 → 2（重度）→ 3（scaffold）→ 4 → 5 → 6。
- **第一步（階段 0 → 2）：** 讀文件；擷取範圍、已鎖定的決定
和功能清單；把它排成**薄的垂直切片**（先做一條端到端
的路徑，不是先做完所有 model 再做所有 view）。階段 3 負責立起第一個切片。
## How It Works
1. 用上面的設定執行 `orch-pipeline` 引擎。
2. **重用既有的 GAN harness**，不要自己手刻迭代迴圈：
- 把 SDD 轉成 `gan-harness/spec.md` + `gan-harness/eval-rubric.md`
（這取代了 `gan-planner` 本來會產生的東西，因為你已經有規格了）。
- 用 `/gan-build "<one-line brief>" --skip-planner` 推動建置
（預設值：`--max-iterations 15`、`--pass-threshold 7.0`、
`--eval-mode playwright`；非 UI 的切片用 `--eval-mode code-only`）。
- 那個指令會跑 `gan-generator` → `gan-evaluator` 迴圈，並寫出
`gan-harness/feedback/feedback-NNN.md`，直到分數通過或停滯。
3. 停在 **Gate 1**（切片計畫）和 **Gate 2**（commit 前）。把
骨架和每個切片分別作為獨立的 `feat:` commit。
4. 任何碰到安全觸發條件的切片，都要加上 `security-reviewer`。
## Example
```
orch-build-mvp: civicpulse/docs/SDD-v0.6.md
→ read SDD → slice list (vertical) → scaffold slice 1 [GATE 1: approve]
→ /gan-build --skip-planner (generator → evaluator loop) scores vs spec → review
→ commit feat: [GATE 2: confirm] → next slice
```英文原文
---
name: orch-build-mvp
description: Orchestrate bootstrapping a working MVP from a design or spec document — ingest the SDD/PRD, plan thin vertical slices, scaffold the first end-to-end slice, then drive a generator-evaluator build loop with review and gated feat commits. Use when a design or spec document must become a running MVP through planned vertical slices.
metadata:
origin: ECC
---
# orch-build-mvp
Actor · action · target: **orch · build · mvp**. Thin wrapper over the shared
engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
## When to Use
- The user has a **design / spec document** (SDD, PRD, system_design) and wants a
working vertical slice bootstrapped from it.
- Takes a doc path as its argument, e.g. `civicpulse/docs/SDD-v0.6.md`.
## Operation settings
- **Default size floor:** large — this is the full pipeline including Scaffold.
- **Phase mask:** 0 (read the spec) → 1 → 2 (heavy) → 3 (scaffold) → 4 → 5 → 6.
- **First move (phase 0 → 2):** read the doc; extract scope, locked decisions,
and the feature list; order it into **thin vertical slices** (one end-to-end
path first, not all-models-then-all-views). Phase 3 stands up that first slice.
## How It Works
1. Run the `orch-pipeline` engine with the settings above.
2. **Reuse the existing GAN harness** instead of hand-rolling an iterate loop:
- Translate the SDD into `gan-harness/spec.md` + `gan-harness/eval-rubric.md`
(this stands in for what `gan-planner` would generate — you already have the spec).
- Drive the build with `/gan-build "<one-line brief>" --skip-planner`
(defaults: `--max-iterations 15`, `--pass-threshold 7.0`,
`--eval-mode playwright`; use `--eval-mode code-only` for non-UI slices).
- That command runs the `gan-generator` → `gan-evaluator` loop and writes
`gan-harness/feedback/feedback-NNN.md` until the score passes or plateaus.
3. Stop at **Gate 1** (slice plan) and **Gate 2** (pre-commit). Commit the
scaffold and each slice as separate `feat:` commits.
4. Add `security-reviewer` for any slice touching a security trigger.
## Example
```
orch-build-mvp: civicpulse/docs/SDD-v0.6.md
→ read SDD → slice list (vertical) → scaffold slice 1 [GATE 1: approve]
→ /gan-build --skip-planner (generator → evaluator loop) scores vs spec → review
→ commit feat: [GATE 2: confirm] → next slice
```