dflow-sdd-ddd 0.1.0 → 0.2.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dflow-sdd-ddd",
-  "version": "0.1.0",
-  "description": "Dflow SDD/DDD project scaffolding CLI",
+  "version": "0.2.0",
+  "description": "Spec-first SDD/DDD workflow kit for AI-assisted development",
   "type": "commonjs",
   "bin": {
     "dflow": "bin/dflow.js",
@@ -12,7 +12,12 @@
   },
   "files": [
     "bin/",
+    "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "docs/",
     "lib/",
+    "TEMPLATE-COVERAGE.md",
+    "TEMPLATE-LANGUAGE-GLOSSARY.md",
     "templates/",
     "README.md"
   ],
@@ -21,17 +26,18 @@
     "ddd",
     "specification-driven-development",
     "domain-driven-design",
-    "codex",
-    "claude-code"
+    "spec-first",
+    "ai-assisted-development",
+    "ai-coding-agent"
   ],
   "repository": {
     "type": "git",
-    "url": "git+ssh://git@github.com/weilung/AI-Guided-SDD-DDD-Development-Skills.git"
+    "url": "git+ssh://git@github.com/weilung/dflow-sdd-ddd.git"
   },
   "bugs": {
-    "url": "https://github.com/weilung/AI-Guided-SDD-DDD-Development-Skills/issues"
+    "url": "https://github.com/weilung/dflow-sdd-ddd/issues"
   },
-  "homepage": "https://github.com/weilung/AI-Guided-SDD-DDD-Development-Skills#readme",
+  "homepage": "https://github.com/weilung/dflow-sdd-ddd#readme",
   "scripts": {
     "test": "node test/smoke.mjs"
   },

package/templates/brownfield/scaffolding/AI-AGENT-GUIDE.md

@@ -0,0 +1,92 @@
+# Dflow AI Agent Guide
+
+This project uses Dflow for spec-first AI-assisted development.
+
+## Project Context
+
+| Field | Value |
+|---|---|
+| Project | {System Name} |
+| Dflow track | {edition} |
+| Project type | {project-type} |
+| Tech stack | {tech-stack-summary} |
+| Migration / legacy context | {migration-context} |
+| Prose language | {prose-language} |
+
+## Before Editing Code
+
+Do not jump from a request directly to code. First identify the matching
+Dflow workflow and confirm the intended path with the developer.
+
+Use these workflow entry points as plain chat instructions if slash commands
+are not available in the current AI tool:
+
+| Workflow | Use when |
+|---|---|
+| `/dflow:new-feature` | A new user-visible capability or business behavior is requested. |
+| `/dflow:modify-existing` | Existing behavior needs to change. |
+| `/dflow:bug-fix` | A defect can be described with expected vs actual behavior. |
+| `/dflow:new-phase` | An active feature needs another implementation slice. |
+| `/dflow:finish-feature` | Implementation is complete and needs drift closure. |
+| `/dflow:verify` | Specs, domain docs, implementation, and tests need consistency checks. |
+| `/dflow:pr-review` | A change is ready for SDD/DDD review. |
+| `/dflow:report-dflow-feedback` | You found a Dflow issue or improvement and want a sanitized upstream feedback draft. |
+
+## Source of Truth
+
+Dflow-owned project documents live under `dflow/specs/`.
+
+| Area | Path |
+|---|---|
+| Shared conventions | `dflow/specs/shared/_conventions.md` |
+| System overview | `dflow/specs/shared/_overview.md` |
+| Domain glossary | `dflow/specs/domain/glossary.md` |
+| Context map | `dflow/specs/domain/context-map.md` |
+| Active feature specs | `dflow/specs/features/active/` |
+| Completed feature snapshots | `dflow/specs/features/completed/` |
+| Technical debt | `dflow/specs/architecture/tech-debt.md` or `dflow/specs/migration/tech-debt.md` |
+
+## Core Rules
+
+1. Spec before code: meaningful behavior changes need a spec or lightweight bug spec before implementation.
+2. Keep domain language explicit: update glossary, rules, models, and behavior snapshots when domain meaning changes.
+3. Keep phase delta, feature snapshot, and system state separate.
+4. Check drift before calling work complete.
+5. Follow `dflow/specs/shared/_conventions.md`, especially `## Prose Language`.
+
+## Pre-V1 Artifacts Detection
+
+When working in a project that adopted Dflow before `dflow-sdd-ddd@0.1.0`,
+you may encounter layout or naming patterns that predate the V1 baseline.
+If any of the following appear, surface the observation to the developer
+and recommend manual migration; do not rewrite anything silently.
+
+Signals:
+
+- Top-level `specs/` directory containing Dflow-shaped content (V1 layout
+  uses `dflow/specs/`).
+- `_共用/` directory under `specs/` or `dflow/specs/` (V1 uses `shared/`).
+- Section headings in Traditional Chinese where V1 templates render
+  canonical English; compare against `TEMPLATE-LANGUAGE-GLOSSARY.md` if
+  available.
+- References to a runtime `/dflow:init-project` slash command (V1
+  replaced it with the shell command `npx dflow-sdd-ddd init`).
+- A root `CLAUDE.md`, `AGENTS.md`, or equivalent that holds the full
+  Dflow workflow text instead of being a thin shim pointing to this
+  file.
+- `dflow/specs/shared/_conventions.md` is missing the `> Dflow Version:`
+  front-matter line (V1 init writes it automatically).
+
+Recommend `docs/migrating-to-dflow-v1.md` for the manual migration
+checklist. Migration affects every spec the team has written; manual
+review is required.
+
+## Tool-Specific Notes
+
+This file is the canonical Dflow guide. Root-level files such as
+`AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, and `.github/copilot-instructions.md`
+should stay thin and point back here.
+
+If a tool does not support Dflow slash commands, treat the command names as
+plain workflow names and execute the matching process from the Dflow skill
+source in this repository.

package/templates/{webforms → brownfield}/scaffolding/CLAUDE-md-snippet.md

@@ -1,17 +1,15 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # CLAUDE.md Snippet — Dflow Adoption
 
 > This file is a **snippet**, not a standalone `CLAUDE.md`. Its purpose
 > is to be merged into your project's root `CLAUDE.md`:
 >
-> - If your project does **not** yet have a `CLAUDE.md`, the
->   `npx dflow-sdd-ddd init` flow will create one using this snippet as
->   the starting content.
-> - If your project **already has** a `CLAUDE.md`, the init flow will
->   copy this file into your repo and prompt you to merge the
->   sections below into the appropriate places in your existing
->   `CLAUDE.md`. No auto-merge — you keep editorial control.
+> - New `npx dflow-sdd-ddd init` output uses
+>   `dflow/specs/shared/AI-AGENT-GUIDE.md` as the canonical guide and
+>   creates a thin `CLAUDE.md` shim that points back to it.
+> - Use this legacy snippet only if you intentionally want the older
+>   Claude-specific two-H2 layout in your project's root `CLAUDE.md`.
 
 The snippet follows the Dflow `templates/CLAUDE.md` H2 segmentation
 (established in PROPOSAL-007c): **System Context** (what the system is)
@@ -93,7 +91,7 @@ src/
 
 AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 （T1/T2/T3）、各 `/dflow:` 命令的具體流程，**全部定義於 Dflow skill
-本體**（`sdd-ddd-webforms-skill/SKILL.md` 與 `references/*.md`）。
+本體**（`sdd-ddd-brownfield-skill/SKILL.md` 與 `references/*.md`）。
 本 `CLAUDE.md` 不重述這些內容，避免雙份維護。
 
 當你作為 AI assistant 被呼叫時，若偵測到使用者需要 SDD/DDD 工作流
@@ -107,6 +105,7 @@ AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 - `/dflow:finish-feature` — feature 收尾
 - `/dflow:pr-review` — PR 審查
 - `/dflow:verify` — rules.md ↔ behavior.md 漂移檢查
+- `/dflow:report-dflow-feedback` — 草擬給 Dflow upstream 的已清理回饋，不自動送出
 - `/dflow:status` / `/dflow:next` / `/dflow:cancel` — 狀態管理
 
 ### Project-Level Supplemental Rules

package/templates/{webforms → brownfield}/scaffolding/Git-principles-gitflow.md

@@ -1,4 +1,4 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # Git Principles — Git Flow edition
 

package/templates/{webforms → brownfield}/scaffolding/Git-principles-trunk.md

@@ -1,4 +1,4 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # Git Principles — Trunk-based / GitHub Flow edition
 

package/templates/{webforms → brownfield}/scaffolding/_conventions.md

@@ -1,8 +1,9 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # Spec Writing Conventions — {System Name}
 
 > Created: {YYYY-MM-DD}
+> Dflow Version: {dflow-version}
 > Scope: how spec documents are authored and named in this project.
 > Audience: engineers writing specs; AI assistants producing spec drafts.
 

package/templates/{webforms → brownfield}/scaffolding/_overview.md

@@ -1,4 +1,4 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # System Overview — {System Name}
 
@@ -105,5 +105,5 @@ Link to any ADR or migration plan doc if one exists.}
   branching-strategy-specific file that matches this project
 - [Glossary](../domain/glossary.md)
 - [Tech debt backlog](../migration/tech-debt.md)
-- Dflow skill: see `CLAUDE.md` and the `sdd-ddd-webforms-skill/` bundle
+- Dflow skill: see `CLAUDE.md` and the `sdd-ddd-brownfield-skill/` bundle
   for the full AI workflow guidance.

package/templates/{webforms → brownfield}/templates/context-map.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Context Map
 

package/templates/{webforms → brownfield}/templates/glossary.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Glossary
 

package/templates/{webforms → brownfield}/templates/models.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Domain Models
 

package/templates/{webforms → brownfield}/templates/phase-spec.md

@@ -173,7 +173,7 @@ Then {新的預期結果}
 
 > AI 在 Phase 4 實作規劃完成後，根據「Implementation Notes」產生的具體任務清單。
 > 格式：`[LAYER]-[NUMBER]: 任務描述`
-> 分類標籤（WebForms 版）：
+> 分類標籤（Brownfield track）：
 >   - `DOMAIN`  — Domain 層類別、VO、Service、Interface
 >   - `PAGE`    — Code-Behind / ASPX 變更
 >   - `DATA`    — 資料表 schema 或 Repository 實作

package/templates/{webforms → brownfield}/templates/rules.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Business Rules
 

package/templates/{webforms → brownfield}/templates/tech-debt.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Migration Tech Debt
 

package/templates/greenfield/scaffolding/AI-AGENT-GUIDE.md

@@ -0,0 +1,92 @@
+# Dflow AI Agent Guide
+
+This project uses Dflow for spec-first AI-assisted development.
+
+## Project Context
+
+| Field | Value |
+|---|---|
+| Project | {System Name} |
+| Dflow track | {edition} |
+| Project type | {project-type} |
+| Tech stack | {tech-stack-summary} |
+| Migration / legacy context | {migration-context} |
+| Prose language | {prose-language} |
+
+## Before Editing Code
+
+Do not jump from a request directly to code. First identify the matching
+Dflow workflow and confirm the intended path with the developer.
+
+Use these workflow entry points as plain chat instructions if slash commands
+are not available in the current AI tool:
+
+| Workflow | Use when |
+|---|---|
+| `/dflow:new-feature` | A new user-visible capability or business behavior is requested. |
+| `/dflow:modify-existing` | Existing behavior needs to change. |
+| `/dflow:bug-fix` | A defect can be described with expected vs actual behavior. |
+| `/dflow:new-phase` | An active feature needs another implementation slice. |
+| `/dflow:finish-feature` | Implementation is complete and needs drift closure. |
+| `/dflow:verify` | Specs, domain docs, implementation, and tests need consistency checks. |
+| `/dflow:pr-review` | A change is ready for SDD/DDD review. |
+| `/dflow:report-dflow-feedback` | You found a Dflow issue or improvement and want a sanitized upstream feedback draft. |
+
+## Source of Truth
+
+Dflow-owned project documents live under `dflow/specs/`.
+
+| Area | Path |
+|---|---|
+| Shared conventions | `dflow/specs/shared/_conventions.md` |
+| System overview | `dflow/specs/shared/_overview.md` |
+| Domain glossary | `dflow/specs/domain/glossary.md` |
+| Context map | `dflow/specs/domain/context-map.md` |
+| Active feature specs | `dflow/specs/features/active/` |
+| Completed feature snapshots | `dflow/specs/features/completed/` |
+| Technical debt | `dflow/specs/architecture/tech-debt.md` or `dflow/specs/migration/tech-debt.md` |
+
+## Core Rules
+
+1. Spec before code: meaningful behavior changes need a spec or lightweight bug spec before implementation.
+2. Keep domain language explicit: update glossary, rules, models, and behavior snapshots when domain meaning changes.
+3. Keep phase delta, feature snapshot, and system state separate.
+4. Check drift before calling work complete.
+5. Follow `dflow/specs/shared/_conventions.md`, especially `## Prose Language`.
+
+## Pre-V1 Artifacts Detection
+
+When working in a project that adopted Dflow before `dflow-sdd-ddd@0.1.0`,
+you may encounter layout or naming patterns that predate the V1 baseline.
+If any of the following appear, surface the observation to the developer
+and recommend manual migration; do not rewrite anything silently.
+
+Signals:
+
+- Top-level `specs/` directory containing Dflow-shaped content (V1 layout
+  uses `dflow/specs/`).
+- `_共用/` directory under `specs/` or `dflow/specs/` (V1 uses `shared/`).
+- Section headings in Traditional Chinese where V1 templates render
+  canonical English; compare against `TEMPLATE-LANGUAGE-GLOSSARY.md` if
+  available.
+- References to a runtime `/dflow:init-project` slash command (V1
+  replaced it with the shell command `npx dflow-sdd-ddd init`).
+- A root `CLAUDE.md`, `AGENTS.md`, or equivalent that holds the full
+  Dflow workflow text instead of being a thin shim pointing to this
+  file.
+- `dflow/specs/shared/_conventions.md` is missing the `> Dflow Version:`
+  front-matter line (V1 init writes it automatically).
+
+Recommend `docs/migrating-to-dflow-v1.md` for the manual migration
+checklist. Migration affects every spec the team has written; manual
+review is required.
+
+## Tool-Specific Notes
+
+This file is the canonical Dflow guide. Root-level files such as
+`AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, and `.github/copilot-instructions.md`
+should stay thin and point back here.
+
+If a tool does not support Dflow slash commands, treat the command names as
+plain workflow names and execute the matching process from the Dflow skill
+source in this repository.

package/templates/{core → greenfield}/scaffolding/CLAUDE-md-snippet.md

@@ -1,24 +1,24 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
-# CLAUDE.md Snippet — Dflow Adoption (Core edition)
+# CLAUDE.md Snippet — Dflow Adoption (Greenfield track)
 
 > Source: `scaffolding/CLAUDE-md-snippet.md`
 > Purpose: a minimal block you paste into (or replace with) your
 > project's root `CLAUDE.md` when adopting Dflow.
-> For the Core skill, the full reference template lives at
-> `sdd-ddd-core-skill/templates/CLAUDE.md` — if you want the complete
-> version, use that instead. This snippet is a lighter starting point.
+> For the Greenfield track, the full reference template lives at
+> `sdd-ddd-greenfield-skill/templates/CLAUDE.md` — if you want the complete
+> legacy Claude-specific version, use that instead. New CLI init output uses
+> `AI-AGENT-GUIDE.md` plus a generated `CLAUDE.md` shim.
 
 ---
 
 ## How to use this snippet
 
-- **If your project has no `CLAUDE.md`**: `npx dflow-sdd-ddd init` will
-  create one using this snippet as the base
-- **If your project already has a `CLAUDE.md`**: do NOT overwrite.
-  Merge the **two H2 blocks** below (`System Context` / `Development Workflow`) into your
-  existing file, preserving any project-specific content you already
-  have
+- New `npx dflow-sdd-ddd init` output uses
+  `dflow/specs/shared/AI-AGENT-GUIDE.md` as the canonical guide and creates
+  a thin `CLAUDE.md` shim that points back to it.
+- Use this legacy snippet only if you intentionally want the older
+  Claude-specific two-H2 layout in your project's root `CLAUDE.md`.
 
 The two-H2 structure (`System Context` / `Development Workflow`) is intentional and must be
 preserved — it matches the Dflow skill's `templates/CLAUDE.md` and
@@ -97,8 +97,8 @@ AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 （T1 Heavy / T2 Light / T3 Trivial）、所有 slash command 的 step-by-step
 流程 **不在此重述**，請以 Dflow skill 本體為準：
 
-- `sdd-ddd-core-skill/SKILL.md`（決策樹 + Slash Commands 總表）
-- `sdd-ddd-core-skill/references/` 內各 flow 文件
+- `sdd-ddd-greenfield-skill/SKILL.md`（決策樹 + Slash Commands 總表）
+- `sdd-ddd-greenfield-skill/references/` 內各 flow 文件
 
 本專案採用的 Dflow entry points：
 - `npx dflow-sdd-ddd init` — 專案初始化（一次性，已執行過）
@@ -108,6 +108,7 @@ AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 - `/dflow:bug-fix` — Bug 修復
 - `/dflow:finish-feature` — Feature 收尾 + 整合摘要
 - `/dflow:pr-review` — PR 審查檢查點
+- `/dflow:report-dflow-feedback` — 草擬給 Dflow upstream 的已清理回饋，不自動送出
 
 ### Core Principles (Project Reaffirmed)
 
@@ -158,7 +159,7 @@ AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 ## Notes
 
 - This snippet is intentionally lighter than
-  `sdd-ddd-core-skill/templates/CLAUDE.md`. If you want the full version
+  `sdd-ddd-greenfield-skill/templates/CLAUDE.md`. If you want the full version
   (with detailed flow descriptions per slash command), use that
   template instead
 - The snippet does NOT re-copy the Dflow decision tree, Ceremony

package/templates/{core → greenfield}/scaffolding/Git-principles-gitflow.md

@@ -1,4 +1,4 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # Git Principles — Git Flow edition
 

package/templates/{core → greenfield}/scaffolding/Git-principles-trunk.md

@@ -1,4 +1,4 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # Git Principles — Trunk-based / GitHub Flow edition
 

package/templates/{core → greenfield}/scaffolding/_conventions.md

@@ -1,8 +1,9 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # Spec Writing Conventions — {System Name}
 
 > Created: {YYYY-MM-DD}
+> Dflow Version: {dflow-version}
 > Scope: how spec documents are authored and named in this project.
 > Audience: engineers writing specs; AI assistants producing spec drafts.
 

package/templates/{core → greenfield}/scaffolding/_overview.md

@@ -1,4 +1,4 @@
-<!-- Scaffolding template maintained alongside Dflow skill. See proposals/PROPOSAL-010 for origin. -->
+<!-- Scaffolding template maintained alongside Dflow skill. See archive/proposals/PROPOSAL-010 for origin. -->
 
 # System Overview — {System Name}
 
@@ -161,5 +161,5 @@ Initial ADRs that typically exist:
 - [Glossary](../domain/glossary.md)
 - [Tech debt backlog](../architecture/tech-debt.md)
 - [Architecture decisions](../architecture/decisions/)
-- Dflow skill: see `CLAUDE.md` and the `sdd-ddd-core-skill/` bundle
+- Dflow skill: see `CLAUDE.md` and the `sdd-ddd-greenfield-skill/` bundle
   for the full AI workflow guidance.

package/templates/{core → greenfield}/scaffolding/architecture-decisions-README.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Architecture Decisions
 

package/templates/{core → greenfield}/templates/context-map.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Context Map
 

package/templates/{core → greenfield}/templates/events.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Domain Events
 

package/templates/{core → greenfield}/templates/glossary.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Glossary
 

package/templates/{core → greenfield}/templates/models.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Domain Models
 

package/templates/{core → greenfield}/templates/phase-spec.md

@@ -178,7 +178,7 @@ And {產生的 Domain Event}
 
 > AI 在 Phase 4 實作規劃完成後，根據「Implementation Plan (Layer by Layer)」產生的具體任務清單。
 > 格式：`[LAYER]-[NUMBER]: 任務描述`
-> 分類標籤（Core 版，對應 Clean Architecture 各層）：
+> 分類標籤（Greenfield track，對應 Clean Architecture 各層）：
 >   - `DOMAIN` — Aggregate、Entity、VO、Domain Event、Domain Service、Repository Interface
 >   - `APP`    — Command/Query、Handler、Validator、DTO、Event Handler
 >   - `INFRA`  — EF Configuration、Repository Impl、外部服務 adapter、Migration

package/templates/{core → greenfield}/templates/rules.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Business Rules
 

package/templates/{core → greenfield}/templates/tech-debt.md

@@ -1,4 +1,4 @@
-<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+<!-- Template maintained by Dflow. See archive/proposals/PROPOSAL-013 for origin. -->
 
 # Architecture Tech Debt