dflow-sdd-ddd 0.7.0 → 0.9.0

package/README.en.md

@@ -35,8 +35,9 @@ npm install -g dflow-sdd-ddd
 dflow init
 ```
 
-The init flow asks whether the project is greenfield or brownfield, then
-previews the files it will create. Existing files are not overwritten. Init
+The init flow asks whether the project is greenfield or brownfield, which Git
+policy the team follows (GitFlow / Trunk), and how AI-made commits should be
+marked, then previews the files it will create. Existing files are not overwritten. Init
 creates workflow documentation and AI instruction files; it does not inspect,
 refactor, or migrate your application code.
 
@@ -317,7 +318,7 @@ Usable only inside an already-started active feature. Targets pointing at `compl
 |---|---|---|
 | `/dflow:verify` | Need to confirm docs, code, tests, and tech-debt records are still in sync | Drift report across spec, domain docs, implementation, tests, and debt records |
 | `/dflow:pr-review` | A change is ready for review | SDD/DDD compliance review checklist with risks, gaps, and follow-up items |
-| `/dflow:report-dflow-feedback` | You or the AI found a Dflow issue or improvement while using it | Sanitized local feedback draft; nothing is submitted automatically |
+| `/dflow:report-dflow-feedback` | You or the AI found a Dflow issue or improvement while using it | Sanitized local draft rendered field-by-field for the upstream issue form, ready to paste; nothing is submitted automatically |
 
 ### What should I run? (rule of thumb)
 
@@ -389,4 +390,4 @@ release history.
 
 ## License
 
-MIT License. See [LICENSE](LICENSE).
+GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later). See [LICENSE](LICENSE).

package/README.md

@@ -33,7 +33,7 @@ npm install -g dflow-sdd-ddd
 dflow init
 ```
 
-init 流程會詢問是 greenfield 或 brownfield，接著預覽即將建立的檔案。既有檔案不會被覆寫。Init 只建立 workflow 文件與 AI 指示檔，**不會**檢查、重構、或遷移你的應用程式碼。
+init 流程會詢問是 greenfield 或 brownfield、團隊採用的 Git policy（GitFlow / Trunk）、以及 AI commit 的標記方式，接著預覽即將建立的檔案。既有檔案不會被覆寫。Init 只建立 workflow 文件與 AI 指示檔，**不會**檢查、重構、或遷移你的應用程式碼。
 
 若專案已初始化、之後又要加入另一個 AI 程式設計工具，執行：
 
@@ -263,7 +263,7 @@ Dflow 指令依角色分四類。「我要做的事」對應到指令的速查
 |---|---|---|
 | `/dflow:verify` | 需要確認文件、程式、測試、債務紀錄是否一致 | 跨規格、領域文件、實作、測試、債務的 drift report |
 | `/dflow:pr-review` | 變更已準備接受審查 | SDD/DDD 合規 review 清單，含風險、缺口、後續項目 |
-| `/dflow:report-dflow-feedback` | 你或 AI 在使用中發現 Dflow 本身的問題 | sanitized 的本地 feedback 草稿；不自動送出 |
+| `/dflow:report-dflow-feedback` | 你或 AI 在使用中發現 Dflow 本身的問題 | sanitized 的本地草稿，逐欄對齊上游 issue 表單可直接貼上；不自動送出 |
 
 ### 該選哪個指令（rule of thumb）
 
@@ -328,4 +328,4 @@ GitHub 上的 source 可能包含 `0.2.0` 之後尚未發佈的 repo 變更。
 
 ## 授權
 
-MIT License，見 [LICENSE](LICENSE)。
+GNU Affero General Public License v3.0 或更新版本（AGPL-3.0-or-later），見 [LICENSE](LICENSE)。

package/bin/dflow.js

@@ -22,8 +22,9 @@ function printInitHelp() {
   dflow init
 
 Initializes Dflow project specs under dflow/specs/.
-The command prompts for project type, tech stack, prose language,
-optional starter files, and AI coding agents before showing a full file preview.
+The command prompts for project type, tech stack, prose language, Git policy,
+AI commit marker, optional starter files, and AI coding agents before showing a
+full file preview.
 `);
 }
 

package/docs/evaluating-dflow.en.md

@@ -35,10 +35,16 @@ in your project's `dflow/specs/` directory and AI instruction files.
   map, architecture/tech-debt, features active/completed). See
   [`README.md` "Files Created by Init"](../README.en.md#files-created-by-init)
   for the full tree.
-- A canonical project guide at `dflow/specs/shared/AI-AGENT-GUIDE.md`.
+- A canonical project guide at `dflow/specs/shared/AI-AGENT-GUIDE.md` —
+  the command registry, routing rules, and project context.
+- A vendored workflow bundle at `dflow/specs/shared/dflow-workflows/` —
+  the executable step definitions for each `/dflow:*` workflow (step gates,
+  completion checklists, templates). This bundle is projected from the npm
+  package at init time so workflows are reachable from any clone without
+  needing the Dflow source or package installed locally.
 - Mergeable AI agent instruction files for the tools you select (e.g.,
   `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`). Each is a
-  thin pointer to the canonical guide.
+  thin pointer to the canonical guide and workflow bundle.
 
 `init` does **not**:
 
@@ -60,7 +66,9 @@ or more tools and Dflow writes the corresponding shim:
 | GitHub Copilot | `.github/copilot-instructions.md` |
 
 Each shim points back to the canonical
-`dflow/specs/shared/AI-AGENT-GUIDE.md`. Practical implications:
+`dflow/specs/shared/AI-AGENT-GUIDE.md`. The guide acts as the command registry
+and router; executable workflow steps live in the vendored bundle at
+`dflow/specs/shared/dflow-workflows/`. Practical implications:
 
 - Multiple tools can be active in the same project without diverging
   workflow rules.
@@ -68,8 +76,9 @@ Each shim points back to the canonical
   `dflow configure-agents` to add another shim, or
   `dflow configure-agents --command-adapters` to opt in to tool-native command
   entries.
-- The project guide stays the single source of truth for Dflow workflow
-  behavior.
+- The guide and workflow bundle together are the authoritative sources for
+  Dflow workflow behavior; both are plain Markdown committed in your repo and
+  accessible to any clone.
 
 `/dflow:*` is the canonical shared vocabulary, but each tool's `/` parser
 behaves differently: Claude Code command adapters use `/dflow:<id>`, the

package/docs/evaluating-dflow.md

@@ -25,8 +25,14 @@ 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`、`.github/copilot-instructions.md`）。每個都是指向 canonical 指南的薄 shim。
+- 位於 `dflow/specs/shared/AI-AGENT-GUIDE.md` 的 canonical 專案指南 ——
+  命令登錄表、路由規則與專案上下文。
+- 位於 `dflow/specs/shared/dflow-workflows/` 的 vendored workflow bundle ——
+  各 `/dflow:*` workflow 的可執行步驟定義（step gates、completion checklists、模板）。
+  這個 bundle 在 init 時從 npm 套件投影進專案，因此 workflow 步驟是 self-contained
+  且可達的，任何 clone 都不需要 Dflow source 或 package 在本機安裝。
+- 你所選工具的可合併 AI 指示檔（例如 `CLAUDE.md`、`AGENTS.md`、`.github/copilot-instructions.md`）。
+  每個都是指向 canonical 指南與 workflow bundle 的薄 shim。
 
 `init` **不會**：
 
@@ -45,11 +51,14 @@ Dflow 支援多種 AI 程式設計助理。跑完 `init` 後，你選取一個
 | Claude Code | `CLAUDE.md` |
 | GitHub Copilot | `.github/copilot-instructions.md` |
 
-每個 shim 都指向 canonical 的 `dflow/specs/shared/AI-AGENT-GUIDE.md`。實際意義：
+每個 shim 都指向 canonical 的 `dflow/specs/shared/AI-AGENT-GUIDE.md`（命令登錄表）
+與 `dflow/specs/shared/dflow-workflows/`（可執行步驟定義）。實際意義：
 
 - 同一個專案可以同時啟用多個工具，而不會有 workflow 規則分歧。
-- 之後切換或新增工具不需要重跑 `init`；執行 `dflow configure-agents` 即可新增 shim，或用 `dflow configure-agents --command-adapters` opt in 工具原生命令入口。
-- 專案指南始終保持為 Dflow workflow 行為的單一 source of truth。
+- 之後切換或新增工具不需要重跑 `init`；執行 `dflow configure-agents` 即可新增 shim，
+  或用 `dflow configure-agents --command-adapters` opt in 工具原生命令入口。
+- 指南與 workflow bundle 共同成為 Dflow workflow 行為的權威來源；兩者都是純 Markdown
+  已 commit 進 repo，任何 clone 均可直接讀取。
 
 `/dflow:*` 是 canonical 共同詞彙，但各工具的 `/` parser 行為不同：Claude Code
 command adapters 使用 `/dflow:<id>`，GitHub Copilot prompt 選單使用

package/docs/using-with-claude-code.en.md

@@ -68,11 +68,15 @@ Two things happen when Claude Code starts in this project:
    Code's Markdown import syntax to inline the canonical Dflow guide. So
    Claude Code effectively reads both files as one set of instructions.
 
-The canonical guide (`dflow/specs/shared/AI-AGENT-GUIDE.md`) is where the
-real workflow rules live: project context (track, tech stack, prose
+The canonical guide (`dflow/specs/shared/AI-AGENT-GUIDE.md`) is the
+**command registry and router**: project context (track, tech stack, prose
 language), the `/dflow:*` workflow table, source-of-truth file paths, and
-core SDD/DDD rules. The `CLAUDE.md` shim stays small precisely so the
-canonical guide can evolve without Claude-Code-specific edits.
+core SDD/DDD rules. The executable workflow steps (Step 1→N, step gates,
+completion checklists) live in the **vendored workflow bundle** that `init`
+projects into `dflow/specs/shared/dflow-workflows/`. Both are plain Markdown
+checked into your repo, so they travel with the project when cloned. The
+`CLAUDE.md` shim stays small precisely so the canonical guide can evolve
+without Claude-Code-specific edits.
 
 If a `CLAUDE.md` already existed in the project, `init` does not overwrite
 it. Instead it writes a merge snippet under `dflow/specs/shared/` that you
@@ -112,9 +116,11 @@ dflow/specs/features/active/. Before I do, I need a short answer on:
 The workflow then walks you through spec drafting, behavior examples,
 implementation planning, and finish-feature drift checks. The exact
 sequence depends on which workflow you entered (`/dflow:new-feature`,
-`/dflow:modify-existing`, `/dflow:bug-fix`, etc.). All workflow definitions
-live under the Dflow skill source; Claude Code follows them by reading the
-skill files when needed.
+`/dflow:modify-existing`, `/dflow:bug-fix`, etc.). The executable step
+definitions (Step 1→N, step gates, completion checklists) are in the
+vendored workflow bundle at `dflow/specs/shared/dflow-workflows/`; `init`
+projects this bundle into every initialized project so the workflow steps
+are self-contained and reachable without any external source dependency.
 
 Available workflow entry points:
 
@@ -215,8 +221,10 @@ After you select Claude Code, Dflow generates a thin skill:
 
 - `.claude/skills/dflow/SKILL.md`
 
-This skill does not copy workflow steps; its body only points to the canonical
-`dflow/specs/shared/AI-AGENT-GUIDE.md`, which carries the real workflow content.
+This skill does not copy workflow steps; its body points to the canonical
+`dflow/specs/shared/AI-AGENT-GUIDE.md` (command registry and routing rules) and
+`dflow/specs/shared/dflow-workflows/` (vendored bundle with executable step
+definitions).
 Its behavior:
 
 - **Auto-triggers on** feature / bug-fix workflows, product/domain behavior

package/docs/using-with-claude-code.md

@@ -62,10 +62,14 @@ Claude Code 在這個專案中啟動時，會發生兩件事：
    Markdown import 語法，將 canonical Dflow 指南 inline 嵌入。因此 Claude Code
    等效於把兩個檔案當成一組指示來讀取。
 
-canonical 指南（`dflow/specs/shared/AI-AGENT-GUIDE.md`）是實際 workflow
-規則的所在：專案上下文（track、技術棧、文章語言）、`/dflow:*` workflow 表、
-source-of-truth 檔案路徑，以及核心 SDD/DDD 規則。`CLAUDE.md` shim 刻意保持精簡，
-這樣 canonical 指南就能在不需要 Claude Code 專屬修改的情況下持續演進。
+canonical 指南（`dflow/specs/shared/AI-AGENT-GUIDE.md`）是**命令登錄表與路由器**：
+專案上下文（track、技術棧、文章語言）、`/dflow:*` workflow 表、source-of-truth
+檔案路徑，以及核心 SDD/DDD 規則。可執行的 workflow 步驟（Step 1→N、step gates、
+completion checklists）則放在 `init` 投影進專案的 **vendored workflow bundle**
+（`dflow/specs/shared/dflow-workflows/`）。兩者都是純 Markdown，隨 repo
+一起 commit，任何 clone 都能直接讀取，不需要 Dflow source 或 package 在本機安裝。
+`CLAUDE.md` shim 刻意保持精簡，這樣 canonical 指南就能在不需要 Claude Code
+專屬修改的情況下持續演進。
 
 如果專案中已有 `CLAUDE.md`，`init` 不會覆蓋它。它改為在
 `dflow/specs/shared/` 下寫入 merge snippet，讓你手動貼入現有的 `CLAUDE.md`。
@@ -103,8 +107,10 @@ dflow/specs/features/active/. Before I do, I need a short answer on:
 接著這個 workflow 會引導你完成 spec 起草、行為範例、實作計畫，以及
 finish-feature 漂移（drift）檢查。確切的流程取決於你進入的是哪個 workflow
 （`/dflow:new-feature`、`/dflow:modify-existing`、`/dflow:bug-fix` 等）。
-所有 workflow 定義都存放在 Dflow skill source 中；Claude Code 在需要時讀取
-skill 檔案來執行它們。
+可執行的步驟定義（Step 1→N、step gates、completion checklists）存放在
+`dflow/specs/shared/dflow-workflows/` 的 vendored bundle 中；`init` 會把這個
+bundle 投影進每個初始化的專案，因此 workflow 步驟是 self-contained 且可達的，
+不需要任何外部 source dependency。
 
 可用的 workflow 入口：
 
@@ -190,8 +196,9 @@ dflow configure-agents --skills
 
 - `.claude/skills/dflow/SKILL.md`
 
-這份 skill 不複製 workflow 步驟，body 只指向 canonical
-`dflow/specs/shared/AI-AGENT-GUIDE.md`，由 guide 承載真正的 workflow 內容。
+這份 skill 不複製 workflow 步驟，body 指向 canonical
+`dflow/specs/shared/AI-AGENT-GUIDE.md`（命令登錄表與路由規則）以及
+`dflow/specs/shared/dflow-workflows/`（含可執行步驟定義的 vendored bundle）。
 它的行為：
 
 - **自動觸發於** feature / bug-fix workflow、product/domain behavior 變更、新需求、

package/docs/using-with-codex.en.md

@@ -162,20 +162,24 @@ triggers only. It does not create Codex command files and it does not add
 equivalent to Claude `.claude/commands` or Copilot `.github/prompts`.
 
 When you select `AGENTS.md - Codex / Copilot coding agent` in
-`--command-adapters` mode and Dflow can create a new `AGENTS.md` shim, the
-shim includes a trigger list generated from the canonical command registry.
-Those triggers are still plain text prompts, for example:
+`--command-adapters` mode, Dflow writes a trigger list generated from the
+canonical command registry into `AGENTS.md`. Those triggers are still plain
+text prompts, for example:
 
 ```text
 dflow:new-feature
 ```
 
-If the project already has a custom `AGENTS.md`, Dflow still preserves that
-file; merge the Dflow pointer manually from the generated snippet or the
-documentation guidance.
+As long as `AGENTS.md` is an unmodified Dflow-generated shim — which is exactly
+the case after the standard `init` → `configure-agents --command-adapters`
+flow — Dflow **injects** the trigger section directly into `AGENTS.md`, wrapped
+in markers, with zero manual merge. Re-running re-projects that same section in
+place instead of appending a duplicate.
 
-In this mode, the Codex-target merge snippet filename is
-`dflow/specs/shared/AGENTS-md-command-adapters-snippet.md`.
+If `AGENTS.md` was edited after Dflow generated it, or is your own custom file,
+Dflow leaves it untouched and instead writes the trigger section to a merge
+snippet for you to merge manually. In that case the Codex-target merge snippet
+filename is `dflow/specs/shared/AGENTS-md-command-adapters-snippet.md`.
 
 ### Version-Control Policy for Generated Artifacts (Codex)
 

package/docs/using-with-codex.md

@@ -149,18 +149,20 @@ Claude `.claude/commands` 或 Copilot `.github/prompts` 對等的 Dflow command-
 adapter。
 
 當你在 `--command-adapters` 模式下選擇 `AGENTS.md - Codex / Copilot coding agent`
-且 Dflow 可以建立新的 `AGENTS.md` shim 時，shim 會加入從 canonical command
-registry 產生的 trigger 清單。這些 trigger 仍是文字提示，例如：
+時，Dflow 會把從 canonical command registry 產生的 trigger 清單寫進 `AGENTS.md`。
+這些 trigger 仍是文字提示，例如：
 
 ```text
 dflow:new-feature
 ```
 
-如果專案已有自訂 `AGENTS.md`，Dflow 仍會保留既有檔案；請依產生的 merge snippet
-或文件指引手動合併 Dflow 指標。
+只要 `AGENTS.md` 是 Dflow 產生且未經改動的 shim（標準 `init` → `configure-agents
+--command-adapters` 流程就是如此），Dflow 會把帶 marker 的 trigger 段**直接注入**
+`AGENTS.md`，零手動合併；重複執行會就地重投影同一段、不會重複附加。
 
-在這個模式下，Codex 目標的 merge snippet 檔名是
-`dflow/specs/shared/AGENTS-md-command-adapters-snippet.md`。
+如果 `AGENTS.md` 在 Dflow 產生後被改過、或本來就是你自訂的檔案，Dflow 會保留既有
+檔案不動，改把 trigger 段寫到 merge snippet 供你手動合併。此情況下 Codex 目標的
+merge snippet 檔名是 `dflow/specs/shared/AGENTS-md-command-adapters-snippet.md`。
 
 ### 產生物的版控政策（Codex）