dflow-sdd-ddd 0.3.0 → 0.5.0

package/CHANGELOG.md

@@ -6,6 +6,124 @@
 
 ---
 
+## 0.5.0 — 2026-05-20 — Guide control commands、opt-in command adapters、移除 Gemini
+
+**Proposals**：PROPOSAL-032（AI-AGENT-GUIDE 補 status/next/cancel 行為語義 +
+scaffolding 單一來源化）、PROPOSAL-033（npm 版 installed 入口 + opt-in command
+adapters）、PROPOSAL-034（移除 Gemini 支援）
+
+**變更**：
+
+- **`/dflow:status` / `/dflow:next` / `/dflow:cancel` 行為語義進入 canonical guide**
+  （PROPOSAL-032）：四份 scaffolding `AI-AGENT-GUIDE.md`（brownfield / greenfield，
+  發佈用 templates 與 skill 副本）的 workflow 表補上這三個控制指令及其行為語義
+  （status 回報格式、next 確認語義、cancel 中止語義）。先前這些定義只存在於不被
+  npm 發佈的 `SKILL.md`，npm-installed 專案的 host AI 拿不到，導致 `/dflow:status`
+  形同失效。
+- **`dflow configure-agents --command-adapters`**（PROPOSAL-033）：新增 opt-in
+  選項，除 thin shim 外額外產生各工具原生的薄 command adapter（Claude
+  `.claude/commands/dflow/dflow-*.md`、Copilot `.github/prompts/dflow-*.prompt.md`，
+  Codex 取得 AGENTS.md command-adapters snippet），讓 `/dflow-*` 指令出現在工具
+  選單。預設不產生；canonical `/dflow:*` 名稱仍以 `AI-AGENT-GUIDE.md` 為準。
+  `docs/using-with-*` 同步更新。
+- **移除 Gemini 支援**（PROPOSAL-034）：`dflow init` / `dflow configure-agents`
+  不再提供 `GEMINI.md` 選項，並刪除 Gemini CLI per-tool docs 與 tutorial shim
+  fixture。
+
+---
+
+## 0.4.0 — 2026-05-19 — Language-agnostic templates and skill source
+
+**Proposals**：PROPOSAL-030（language-agnostic templates and skill source；
+post-v0.3.0 follow-up; cross-model reviewed with Codex CLI）
+
+**變更**：
+
+- **`lib/init.js` canonical placeholders + backward-compat aliases**（PROPOSAL-030 Group 1）：
+  - 新增 canonical placeholders：`{Language}` / `{Framework}` /
+    `{Framework version}` / `{ORM / persistence}` / `{ORM version}` /
+    `{Mediator}`（與既有 `{Test framework}` 對齊）
+  - 既有 .NET-specific placeholder（`{ASP.NET Core version}` /
+    `{EF Core version}` / `{MediatR version}` / `{ASP.NET WebForms version}` /
+    `{.NET Framework version}` / `{ORM / Data Access}`）保留為 backward-compat
+    alias，substitute 同 canonical 值
+  - `extractTechStackPlaceholders` regex 擴充：Spring Boot / NestJS /
+    Fastify / Express / Django / FastAPI / Flask / Gin / Echo / Laravel
+    framework；EF Core / Hibernate / Spring Data JPA / SQLAlchemy /
+    Prisma / TypeORM / MikroORM / GORM / Eloquent / Doctrine ORM；JUnit /
+    Vitest / Jest / Mocha / pytest / unittest / go test / PHPUnit / Pest
+    test framework；C# / TypeScript / JavaScript / Kotlin / Java /
+    Python / Go / PHP / Ruby language
+  - `detectProjectSignals` 加 `stackHints`（從 `pom.xml` / `package.json` /
+    `pyproject.toml` / `go.mod` / `Cargo.toml` / `composer.json` / `Gemfile`
+    fingerprint）— **不**自動推 `trackHint`，user 選擇仍主導
+  - `printNextSteps` 加 `docs/examples-by-stack.md` pointer
+- **Brownfield skill source + templates language-agnostic**（Group 2 + Group 2 follow-up）：
+  - `Code-Behind` → umbrella `business logic embedded in delivery/entrypoint
+    code`，context 簡寫 `presentation-layer logic` (web/UI/API) 或
+    `entrypoint-layer logic` (CLI/batch/pipeline)
+  - `ASP.NET Core migration` / `future ASP.NET Core migration` →
+    `target architecture`
+  - `No System.Web references` → `No delivery-framework references`，明列
+    HTTP req/resp、session/cookie、job-runner context、CLI flag parser、
+    ViewState equivalents 等多 stack 示例
+  - `純 C# class` → `framework-pure class`
+  - Layer tag `PAGE` → `DELIVERY`（含 lightweight-spec 的 layer tags
+    說明擴及 web/CLI/job/pipeline）
+  - SKILL.md 新增 `## Scope: When Dflow Brownfield Applies` 段，明標適用
+    business-rule-bearing legacy systems / 不適用純 infra script 或無
+    domain model pipeline
+  - 目錄樹 `src/Pages/` → `src/Delivery/`（與 umbrella term 對齊）
+  - SKILL.md / templates/CLAUDE.md / scaffolding/CLAUDE-md-snippet.md /
+    scaffolding/_overview.md 在 directory tree 前加 stack-adapt callout
+- **Greenfield skill source + templates language-agnostic**（Group 3 + Group 3 follow-up）：
+  - 檔案標題 `# Project — ASP.NET Core + DDD` →
+    `# Project — Clean Architecture + DDD`
+  - `# X Workflow — ASP.NET Core` → `# X Workflow — Greenfield Clean Architecture`
+  - Cross-edition `Same as WebForms version` → `Same as Brownfield edition`
+  - `_overview.md` stack table 全用 canonical placeholders
+  - `init-project-flow.md` Q2 prompt + substitution table 改 canonical
+  - Project Layout `{Project}.Domain` `.NET` 慣例保留 + 加詳細 callout
+    列 Java/Spring、Node/TS、Python、Go、PHP/Laravel 對應
+  - `PRACTICE_PLAN_tw.md` 開頭加 disclaimer：練習以 .NET 為示例、
+    Dflow 本身 language-agnostic
+  - Git-principles-{gitflow,trunk} 的 `NuGet dependencies` →
+    `external package dependencies`
+- **`docs/examples-by-stack.md` 新增**（Group 4）：520 行 public
+  appendix，列 7 stack 段（.NET ASP.NET Core greenfield / .NET WebForms
+  brownfield / Java Spring Boot / Node TypeScript NestJS / Python FastAPI /
+  Go Gin / PHP Laravel），每段：substituted stack table + project
+  layout + per-stack domain purity check + test framework + run
+  command。`README.md` / `README.en.md` 在 Project Tracks 段加 link。
+- **`planning/init-contract-spec.md` 同步**（Group 1）：placeholder
+  inventory + alias table + detectProjectSignals stackHints 文件對齊
+
+**Breaking / migration notes**：
+
+- **無 runtime API 破壞**：v0.3.0 寫入 user project 的 `CLAUDE.md` /
+  `_overview.md` 等檔案 Dflow 不會自動覆蓋；backward-compat alias 只保護
+  future init 動作的 placeholder 替換不破壞，不主動 migrate 既有檔案
+- 若要對齊新風格，請參考 `docs/examples-by-stack.md` 對既有 init 產出的
+  檔案手動修改
+- AI agent 對話中讀 skill source 會自動切到新術語（Code-Behind →
+  delivery/entrypoint code、ASP.NET Core migration → target architecture）；
+  若 user 有自製 prompt / shortcut 用到舊術語，建議同步更新但**不強制**
+
+**驗證**：
+
+- `npm test`（含新增 Java/Spring Boot greenfield init e2e，assert 不殘留 .NET literals）
+- `scripts/check-repo-consistency.sh`（source ↔ packaged mirror diff clean）
+- 全 repo grep `Code-Behind` / `ASP.NET` / `WebForms` / `NuGet` 在 active skill / template surface 範圍內無殘留（archive/ 與 test fixture 刻意保留）
+
+**邊界**：
+
+- Tutorial 目錄 `tutorial/**` scenario prose 為教學劇情 artifact，明確
+  out of scope（PROPOSAL-030 §影響範圍 已宣告）
+- `test/smoke.mjs` 既有 .NET fixture 保留作為 brownfield init 測試輸入
+- Dist projection 在所有 Group merge 完後一次性 export（Director-only）
+
+---
+
 ## 0.3.0 — 2026-05-18 — Workflow flow completion, terminology disambiguation, bilingual public docs
 
 **Proposals**：PROPOSAL-022（CLI install 推薦路徑）、PROPOSAL-023（line-ending normalization）、PROPOSAL-024（README zh-TW + migration reframing）、PROPOSAL-025（Phase 術語拆解：Step Gate / Activity）、PROPOSAL-026（`/dflow:new-phase` 補 implementation / verification）、PROPOSAL-027（handoff lifecycle，dev-only）、PROPOSAL-028（`docs/*.md` 雙語化）、PROPOSAL-029（tutorial 檔名 align）。

package/README.en.md

@@ -20,7 +20,7 @@ The goal is not the process itself, but repeatable software change with clearer
 | **Three-layer documentation model** | Matches how feature branches actually evolve: phase (one propose-implement-archive cycle) / feature (the whole branch's running state and resume pointer) / system (cross-feature long-term knowledge). Many spec tools only ship phase + system, which breaks down when a feature branch spans multiple phases. Detailed below. |
 | **Change-depth-based tiers (T1/T2/T3)** | AI scales specification and verification by change depth: color/typo gets one inline row in `_index.md`; bug fixes get a lightweight spec plus focused verification; new features or bounded-context-level changes go through a full phase-spec plus layer-by-layer implementation planning / verification. Small changes don't get dragged down by the process. |
 | **Drift verification** | `/dflow:verify` cross-checks specs, domain documents, implementation, tests, and tech-debt records to surface the "documentation still describes the old behavior" drift that PR review by eye usually misses. |
-| **Multi-AI-tool rule sharing** | A canonical project guide plus thin tool-specific shims (`CLAUDE.md` / `AGENTS.md` / `GEMINI.md` / Copilot instructions) — teams switching between Claude, Codex, Gemini, and Copilot don't have to maintain multiple copies of workflow rules. |
+| **Multi-AI-tool rule sharing** | A canonical project guide plus thin tool-specific shims (`CLAUDE.md` / `AGENTS.md` / Copilot instructions) — teams switching between Claude, Codex, and Copilot don't have to maintain multiple copies of workflow rules. |
 
 ## Get Started
 
@@ -113,15 +113,15 @@ Greenfield and Brownfield workflows with worked spec outputs, see the
 | **Greenfield** | You are starting a new system or a new bounded area with room to shape architecture and domain model early. | Clean spec baseline, domain model ownership, feature-by-feature implementation through SDD. |
 | **Brownfield** | You are adding or changing behavior in an existing codebase where business rules may already be scattered. | Progressive domain extraction, safer change planning, and migration-ready domain knowledge. |
 
-These tracks describe adoption style, not framework branding. Dflow should be read as a workflow system for software teams that want AI assistance without giving up domain clarity.
+These tracks distinguish the project's starting state (new vs existing codebase), not a framework choice; the design makes no assumption about language or stack. Dflow should be read as a workflow system for software teams that want AI assistance without giving up domain clarity.
 
-### Track Choice and Migration
+Filled-in examples for common stacks (.NET, Java/Spring, Node/TypeScript, Python, Go, PHP/Laravel) are in [`docs/examples-by-stack.md`](./docs/examples-by-stack.md).
 
-> The "rewrite to ASP.NET Core" path below is the default migration story baked into the current Dflow templates (reflecting Dflow's initial C# / ASP.NET use case), but the design itself is language- and framework-agnostic — the workflow, tier system, and documentation model work for any stack.
+### Track Choice and Migration
 
-Track is fixed at `dflow init` time and **cannot be switched in-place** (there is no `/dflow:switch-to-greenfield` command). Brownfield is by design a preparation path toward Greenfield: pure C# code extracted into `src/Domain/` and the domain documents under `dflow/specs/domain/` (glossary, rules, models, events) are all migration-ready assets — at the eventual rewrite (new ASP.NET Core project + fresh `dflow init` with Greenfield track), they can be lifted directly. `dflow/specs/migration/tech-debt.md` is the brownfield-specific migration debt log.
+Track is fixed at `dflow init` time and **cannot be switched in-place** (there is no `/dflow:switch-to-greenfield` command). Brownfield is by design a preparation path toward Greenfield: domain code extracted into the project's domain layer (e.g., `src/Domain/`) and the domain documents under `dflow/specs/domain/` (glossary, rules, models, events) are all migration-ready assets — at the eventual rewrite (a new project + fresh `dflow init` with Greenfield track), they can be lifted directly. `dflow/specs/migration/tech-debt.md` is the brownfield-specific migration debt log.
 
-Per-BC migration is also supported — once a Bounded Context's logic is fully extracted into `src/Domain/` and the Code-Behind is reduced to UI binding, that BC is already in a Clean Architecture state; the whole system doesn't have to switch in one go. The brownfield `/dflow:modify-existing`'s "assess Code-Behind" step becomes a no-op for that BC naturally.
+Per-BC migration is also supported — once a Bounded Context's business logic is fully extracted into the domain layer and the presentation layer is reduced to UI binding, that BC is already in a Clean Architecture state; the whole system doesn't have to switch in one go. The brownfield `/dflow:modify-existing`'s "assess presentation-layer business logic" step becomes a no-op for that BC naturally.
 
 ## Workflow Model
 
@@ -208,7 +208,6 @@ files whose only job is to redirect the tool to the canonical guide):
 |---|---|
 | Codex / Copilot coding agent | `AGENTS.md` |
 | Claude Code | `CLAUDE.md` |
-| Gemini CLI | `GEMINI.md` |
 | GitHub Copilot | `.github/copilot-instructions.md` |
 
 If one of those files already exists, Dflow leaves it unchanged and writes a
@@ -225,7 +224,6 @@ workflow commands appear in a given AI tool, see the per-tool guides under
 
 - [Using Dflow with Claude Code](docs/using-with-claude-code.en.md)
 - [Using Dflow with Codex CLI](docs/using-with-codex.en.md)
-- [Using Dflow with Gemini CLI](docs/using-with-gemini-cli.en.md)
 - [Using Dflow with GitHub Copilot](docs/using-with-github-copilot.en.md)
 
 Init does not copy the `tutorial/` directory into your project. The
@@ -330,7 +328,7 @@ npm package is `0.2.0`, covering:
 
 - Project initialization (`dflow init`)
 - Workflow documentation (the `/dflow:*` flows)
-- Multi-AI agent setup (CLAUDE.md / AGENTS.md / GEMINI.md / Copilot instructions shims)
+- Multi-AI agent setup (CLAUDE.md / AGENTS.md / Copilot instructions shims)
 - AI-agent-readable SDD/DDD guidance
 - Public migration tooling: manual migration guide plus `dflow doctor` read-only health check
 - Public onboarding: evaluator guide and per-tool walkthroughs for Claude Code and Codex CLI

package/README.md

@@ -20,7 +20,7 @@ Dflow 是一套 spec-first 的工作流程工具集，專為 AI 輔助軟體開
 | **三層文件模型** | 對應 feature branch 的實際節奏：phase（單次提案-實作循環）/ feature（整條 branch 的累積狀態與接續指引）/ system（跨 feature 的長期知識）。許多 spec 工具只有 phase + system 兩層，多次迭代的 feature branch 跨多個 phase 時就會失真。下方有完整說明。 |
 | **依改動深淺的 Tier 制（T1/T2/T3）** | AI 依改動深淺自動決定規格與驗證量級：改顏色 / typo 只需 `_index.md` 一行；bug fix 用 lightweight spec + 聚焦驗證；新 feature 或動到 bounded context 才走完整 phase-spec + 分層實作計畫 / 驗證。小修改不會被流程拖累。 |
 | **漂移驗證** | `/dflow:verify` 把規格、領域文件、實作、測試、技術債紀錄做交叉比對，找出 PR review 人眼看不出來的「文件還在描述舊行為」漂移。 |
-| **多 AI 工具共用一份規則** | Canonical 專案指南 + 各工具薄 shim（`CLAUDE.md` / `AGENTS.md` / `GEMINI.md` / Copilot instructions），團隊在 Claude / Codex / Gemini / Copilot 之間切換時不必維護多份 workflow 規則。 |
+| **多 AI 工具共用一份規則** | Canonical 專案指南 + 各工具薄 shim（`CLAUDE.md` / `AGENTS.md` / Copilot instructions），團隊在 Claude / Codex / Copilot 之間切換時不必維護多份 workflow 規則。 |
 
 ## 開始使用
 
@@ -83,24 +83,24 @@ dflow doctor
 
 第一次採用建議用 branch 或一次性試用專案，讓團隊先檢視產生的 `dflow/specs/` 工作區，再把流程引入正式程式碼。
 
-完整評估流程（init 產生哪些檔案、AI 工具支援、track 選擇、30 分鐘試用 playbook）見 [評估 Dflow](docs/evaluating-dflow.md)。Greenfield 與 Brownfield 端到端劇情走完與規格範例見 [`tutorial/`](tutorial/README.md) 索引。
+完整評估流程（init 產生哪些檔案、AI 工具支援、模式選擇、30 分鐘試用 playbook）見 [評估 Dflow](docs/evaluating-dflow.md)。Greenfield 與 Brownfield 端到端劇情走完與規格範例見 [`tutorial/`](tutorial/README.md) 索引。
 
-## 專案 Track
+## 專案模式
 
-| Track | 何時用 | 主要產出 |
+| 模式 | 何時用 | 主要產出 |
 |---|---|---|
 | **Greenfield** | 新系統或新 bounded area，有空間早期塑形架構與領域模型 | 乾淨的規格 baseline、領域模型歸屬、feature-by-feature SDD 實作 |
 | **Brownfield** | 在既有 codebase 增加或修改行為，業務規則可能已散落各處 | 漸進的領域抽出、更安全的變更規劃、可遷移的領域知識 |
 
-兩條 track 描述的是採用風格，不是 framework 品牌。Dflow 本質是給「希望 AI 協助、又不願放棄領域清晰度」的軟體團隊使用的 workflow 系統。
+兩種模式區分的是專案起始狀態（新建 vs 既有 codebase），不是 framework 品牌；Dflow 對語言與 stack 不做假設，workflow、tier 制與文件模型可套用任何技術組合。本質是給「希望 AI 協助、又不願放棄領域清晰度」的軟體團隊使用的 workflow 系統。
 
-### Track 選擇與遷移
+各 stack（.NET / Java-Spring / Node-TS / Python / Go / PHP-Laravel）的填好範例見 [`docs/examples-by-stack.md`](./docs/examples-by-stack.md)。
 
-> 以下「rewrite 到 ASP.NET Core」是目前 Dflow 模板的預設遷移路徑（出於主要使用者背景），但設計本身與語言 / framework 無關 — workflow、ceremony tier、文件模型都可套用其他 stack。
+### 模式選擇與遷移
 
-Track 在 `dflow init` 時選定、之後**不能 in-place 切換**（沒有 `/dflow:switch-to-greenfield` 之類的指令）。Brownfield 設計上是 Greenfield 的前置準備：抽出到 `src/Domain/` 的純 C# 程式碼與 `dflow/specs/domain/` 內的領域文件（術語、規則、模型、事件）都是 migration-ready 資產，未來 rewrite 時（建新 ASP.NET Core 專案 + 新 `dflow init` 選 Greenfield）可以直接搬過去。`dflow/specs/migration/tech-debt.md` 是 brownfield 專用的遷移債紀錄。
+模式在 `dflow init` 時選定、之後**不能 in-place 切換**（沒有 `/dflow:switch-to-greenfield` 之類的指令）。Brownfield 設計上是 Greenfield 的前置準備：抽出到專案 domain 層（例如 `src/Domain/`）的領域程式碼，與 `dflow/specs/domain/` 內的領域文件（術語、規則、模型、事件），都是 migration-ready 資產 — 未來要 rewrite 時（建新專案 + 新 `dflow init` 選 Greenfield），可以直接搬過去。`dflow/specs/migration/tech-debt.md` 是 brownfield 專用的遷移債紀錄。
 
-也支援「逐 BC（Bounded Context）遷移」— 某個 BC 已純化到 `src/Domain/`、Code-Behind 已純為 UI 綁定後，這個 BC 就已是 Clean Architecture 狀態，不必整個 system 一次性切。brownfield 的 `/dflow:modify-existing` 內「assess Code-Behind」步驟對該 BC 自然會變 no-op。
+也支援「逐 BC（Bounded Context）遷移」— 某個 BC 的業務邏輯已純化到 domain 層、表現層只剩 UI 綁定後，這個 BC 就已是 Clean Architecture 狀態，不必整個 system 一次性切。Brownfield 的 `/dflow:modify-existing` 內「評估表現層業務邏輯」步驟對該 BC 自然會變 no-op。
 
 ## Workflow 模型
 
@@ -184,7 +184,6 @@ Dflow 也會為你的 AI 程式設計助理建立或提供可合併的專案指
 |---|---|
 | Codex / Copilot coding agent | `AGENTS.md` |
 | Claude Code | `CLAUDE.md` |
-| Gemini CLI | `GEMINI.md` |
 | GitHub Copilot | `.github/copilot-instructions.md` |
 
 若這些檔案已存在，Dflow 不會覆蓋，改寫 merge snippet 到 `dflow/specs/shared/`。專案指南保持單一 source of truth，團隊就能用多個 AI 工具而不必維護多份 workflow 規則。
@@ -195,7 +194,6 @@ Dflow 也會為你的 AI 程式設計助理建立或提供可合併的專案指
 
 - [在 Claude Code 中使用 Dflow](docs/using-with-claude-code.md)
 - [在 Codex CLI 中使用 Dflow](docs/using-with-codex.md)
-- [在 Gemini CLI 中使用 Dflow](docs/using-with-gemini-cli.md)
 - [在 GitHub Copilot 中使用 Dflow](docs/using-with-github-copilot.md)
 
 Init 不會把 `tutorial/` 目錄複製進你的專案。[`tutorial/`](tutorial/README.md) 目錄存放在本 source repository，作為理解 Dflow 如何在 Greenfield / Brownfield 劇情中運作的評估材料。
@@ -292,7 +290,7 @@ Dflow 目前以 `dflow-sdd-ddd` 名稱發佈於 npm。最新發佈版本為 `0.2
 
 - 專案初始化（`dflow init`）
 - Workflow 文件（`/dflow:*` 流程）
-- 多 AI agent 設定（CLAUDE.md / AGENTS.md / GEMINI.md / Copilot instructions shim）
+- 多 AI agent 設定（CLAUDE.md / AGENTS.md / Copilot instructions shim）
 - AI agent 可讀的 SDD/DDD 指引
 - 公開 migration tooling：手動 migration guide 與 `dflow doctor` 唯讀健康檢查
 - 公開 onboarding：evaluator 指南、Claude Code / Codex CLI 的 per-tool walkthrough

package/TEMPLATE-COVERAGE.md

@@ -24,7 +24,7 @@ The matrix lists Brownfield / Greenfield logical template parity so reviewers ca
 | Tech debt | Brownfield: `dflow/specs/migration/tech-debt.md`; Greenfield: `dflow/specs/architecture/tech-debt.md` | `templates/tech-debt.md` | `templates/tech-debt.md` | Same backlog intent | Brownfield migration focus; Greenfield architecture focus | - |
 | ADR guide | `dflow/specs/architecture/decisions/README.md` | n/a | `scaffolding/architecture-decisions-README.md` | Greenfield only | Brownfield not applicable | - |
 | Project AI guide | `dflow/specs/shared/AI-AGENT-GUIDE.md` when at least one AI agent is selected during init | `scaffolding/AI-AGENT-GUIDE.md` | `scaffolding/AI-AGENT-GUIDE.md` | Same canonical tool-neutral workflow guide and source-of-truth pointers | Track-specific seeded values and available source-of-truth paths may differ | - |
-| AI tool shims | `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `.github/copilot-instructions.md`, or merge snippets under `dflow/specs/shared/` | generated by CLI | generated by CLI | Thin files must point back to `dflow/specs/shared/AI-AGENT-GUIDE.md`; existing files are not overwritten | Tool-specific import hints differ | - |
+| AI tool shims | `AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, or merge snippets under `dflow/specs/shared/` | generated by CLI | generated by CLI | Thin files must point back to `dflow/specs/shared/AI-AGENT-GUIDE.md`; existing files are not overwritten | Tool-specific import hints differ | - |
 | Legacy Claude guide template | `<project root>/CLAUDE.md` | `templates/CLAUDE.md` | `templates/CLAUDE.md` | H2 navigation and H3 structural headings aligned (canonical English, per F-01 Path A) | Greenfield includes Aggregate / Architecture Decisions and other Greenfield-specific H3 sections | - |
 
 ## Reference Flow Parity

package/bin/dflow.js

@@ -29,12 +29,15 @@ optional starter files, and AI coding agents before showing a full file preview.
 
 function printConfigureAgentsHelp() {
   process.stdout.write(`Usage:
-  dflow configure-agents
+  dflow configure-agents [--command-adapters]
 
 Adds AI agent instruction files to an existing Dflow project.
-The command can create AGENTS.md, CLAUDE.md, GEMINI.md, and
+The command can create AGENTS.md, CLAUDE.md, and
 .github/copilot-instructions.md shims that point to the canonical
 dflow/specs/shared/AI-AGENT-GUIDE.md file.
+
+Options:
+  --command-adapters  Also generate tool-native thin wrappers for supported tools.
 `);
 }
 
@@ -91,8 +94,10 @@ async function main() {
       return 0;
     }
 
-    if (args.length > 1) {
-      process.stderr.write(`Unsupported configure-agents option: ${args.slice(1).join(' ')}\n`);
+    const configureOptions = args.slice(1);
+    const unsupportedConfigureOptions = configureOptions.filter((arg) => arg !== '--command-adapters');
+    if (unsupportedConfigureOptions.length > 0) {
+      process.stderr.write(`Unsupported configure-agents option: ${unsupportedConfigureOptions.join(' ')}\n`);
       return 1;
     }
 
@@ -100,7 +105,8 @@ async function main() {
       cwd: process.cwd(),
       stdin: process.stdin,
       stdout: process.stdout,
-      stderr: process.stderr
+      stderr: process.stderr,
+      commandAdapters: configureOptions.includes('--command-adapters')
     });
   }
 

package/docs/evaluating-dflow.en.md

@@ -37,9 +37,8 @@ in your project's `dflow/specs/` directory and AI instruction files.
   for the full tree.
 - A canonical project guide at `dflow/specs/shared/AI-AGENT-GUIDE.md`.
 - Mergeable AI agent instruction files for the tools you select (e.g.,
-  `CLAUDE.md`, `AGENTS.md`, `GEMINI.md`,
-  `.github/copilot-instructions.md`). Each is a thin pointer to the
-  canonical guide.
+  `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`). Each is a
+  thin pointer to the canonical guide.
 
 `init` does **not**:
 
@@ -58,7 +57,6 @@ or more tools and Dflow writes the corresponding shim:
 |---|---|
 | Codex / Copilot coding agent | `AGENTS.md` |
 | Claude Code | `CLAUDE.md` |
-| Gemini CLI | `GEMINI.md` |
 | GitHub Copilot | `.github/copilot-instructions.md` |
 
 Each shim points back to the canonical
@@ -81,7 +79,6 @@ commands appear in conversation, see the per-tool guides:
 
 - [Using Dflow with Claude Code](using-with-claude-code.en.md)
 - [Using Dflow with Codex CLI](using-with-codex.en.md)
-- [Using Dflow with Gemini CLI](using-with-gemini-cli.en.md)
 - [Using Dflow with GitHub Copilot](using-with-github-copilot.en.md)
 
 ## Greenfield or Brownfield: Choosing a Track

package/docs/evaluating-dflow.md

@@ -26,7 +26,7 @@ Dflow 是 Markdown-based 的 workflow 材料加上一個 scaffolding CLI。它
 - `dflow/specs/` workspace（概覽、慣例、領域詞彙表、context map、架構 / 技術債、功能 active/completed）。完整目錄樹見
   [`README.md` "Init 產生的檔案"](../README.md#init-產生的檔案)。
 - 位於 `dflow/specs/shared/AI-AGENT-GUIDE.md` 的 canonical 專案指南。
-- 你所選工具的可合併 AI 指示檔（例如 `CLAUDE.md`、`AGENTS.md`、`GEMINI.md`、`.github/copilot-instructions.md`）。每個都是指向 canonical 指南的薄 shim。
+- 你所選工具的可合併 AI 指示檔（例如 `CLAUDE.md`、`AGENTS.md`、`.github/copilot-instructions.md`）。每個都是指向 canonical 指南的薄 shim。
 
 `init` **不會**：
 
@@ -43,7 +43,6 @@ Dflow 支援多種 AI 程式設計助理。跑完 `init` 後，你選取一個
 |---|---|
 | Codex / Copilot coding agent | `AGENTS.md` |
 | Claude Code | `CLAUDE.md` |
-| Gemini CLI | `GEMINI.md` |
 | GitHub Copilot | `.github/copilot-instructions.md` |
 
 每個 shim 都指向 canonical 的 `dflow/specs/shared/AI-AGENT-GUIDE.md`。實際意義：
@@ -58,7 +57,6 @@ Dflow 支援多種 AI 程式設計助理。跑完 `init` 後，你選取一個
 
 - [在 Claude Code 中使用 Dflow](using-with-claude-code.md)
 - [在 Codex CLI 中使用 Dflow](using-with-codex.md)
-- [在 Gemini CLI 中使用 Dflow](using-with-gemini-cli.md)
 - [在 GitHub Copilot 中使用 Dflow](using-with-github-copilot.md)
 
 ## Greenfield 或 Brownfield：選擇 Track