dflow-sdd-ddd 0.2.0 → 0.3.0

package/templates/greenfield/templates/phase-spec.md

@@ -19,17 +19,20 @@ Template note (for AI):
   `phase-spec-YYYY-MM-DD-{slug}.md` placed at
   `dflow/specs/features/active/{SPEC-ID}-{slug}/`.
 
-  Each section below carries an HTML comment indicating its fill-in phase (Phase 1-4).
-  These phase markers let /dflow:status and the completion checklist track progress.
-  Phases correspond to SKILL.md § Guiding Questions by Phase:
-    Phase 1 - Understanding (What & Why)
-    Phase 2 - Domain Modeling (BC, Aggregate, VO, Events)
-    Phase 3 - Spec Writing (Behavior + Rules + Edge Cases)
-    Phase 4 - Implementation Planning (layer-by-layer)
-  The "Implementation Tasks" section at the end is generated by AI after Phase 4 planning is done
+  Each section below carries an HTML comment indicating its fill-in activity (Activity 1-4).
+  These activity markers let /dflow:status and the completion checklist track progress.
+  Activities correspond to SKILL.md § Guiding Questions by Activity:
+    Activity 1: Understanding (What & Why)
+    Activity 2: Domain Modeling (BC, Aggregate, VO, Events)
+    Activity 3: Spec Writing (Behavior + Rules + Edge Cases)
+    Activity 4: Implementation Planning (layer-by-layer)
+  The "Implementation Tasks" section at the end is generated by AI after Activity 4 (Implementation Planning) is done
   (see new-feature-flow.md Step 5 end / new-phase-flow.md Step 4 end /
    modify-existing-flow.md Step 3 end).
 
+  Note: "phase 2+ specs" / "Phase 2+" in the BR and Delta sections below refers to
+  the N-th phase-spec of this feature (i.e. iteration unit), NOT an activity number.
+
   For phase 2+ specs in the same feature: only list BRs that are NEW or
   MODIFIED in this phase under "Business Rules"; do not re-copy unchanged BRs from
   prior phases. The cumulative state lives in the feature's `_index.md`
@@ -37,11 +40,11 @@ Template note (for AI):
   bounded context's `rules.md` / `behavior.md` (synced at /dflow:finish-feature).
 -->
 
-## Problem Description <!-- Fill timing: Phase 1 -->
+## Problem Description <!-- Fill timing: Activity 1: Understanding -->
 
 > 用使用者的角度描述，避免技術用語。
 
-## Domain Concepts <!-- Fill timing: Phase 2 -->
+## Domain Concepts <!-- Fill timing: Activity 2: Domain Modeling -->
 
 涉及的 Domain 概念（引用 `dflow/specs/domain/{context}/models.md`）：
 
@@ -55,7 +58,7 @@ Template note (for AI):
 - [ ] `dflow/specs/domain/{context}/events.md` — Domain Events
 
 <!-- dflow:section behavior-scenarios -->
-## Behavior Scenarios <!-- Fill timing: Phase 3 -->
+## Behavior Scenarios <!-- Fill timing: Activity 3: Spec Writing -->
 
 ### Main Success Scenario
 
@@ -76,7 +79,7 @@ Scenario: {替代情境}
   Then {不同結果}
 ```
 
-## Business Rules <!-- Fill timing: Phase 3 -->
+## Business Rules <!-- Fill timing: Activity 3: Spec Writing -->
 
 > Phase 2+ 注意：本段僅列**本 phase 新增 / 修改到的 BR**；未變動的 BR 不重抄
 > （它們的當前狀態見 feature 的 `_index.md` Current BR Snapshot 表）。
@@ -86,7 +89,7 @@ Scenario: {替代情境}
 | BR-01 | {規則描述} | Domain: {Entity/VO/Service} |
 | BR-02 | {規則描述} | Domain: {Entity/VO/Service} |
 
-## Delta from prior phases <!-- Fill timing: Phase 3; skip for the first phase -->
+## Delta from prior phases <!-- Fill timing: Activity 3: Spec Writing; skip for the first phase -->
 
 > 本段僅記**本 phase 相對前一 phase 的變化**，不累積歷史。歷史由 feature 目錄下
 > 各 phase-spec 的本段串接閱讀；feature 層的當前累積狀態見 `_index.md` 的
@@ -122,19 +125,19 @@ And {產生的 Domain Event}
 - BR-003 金額上限
 - BR-005 提交後不可修改
 
-## Edge Cases <!-- Fill timing: Phase 3 -->
+## Edge Cases <!-- Fill timing: Activity 3: Spec Writing -->
 
 | ID | Case | Expected Handling |
 |---|---|---|
 | EC-01 | {邊界描述} | {處理方式} |
 
-## Domain Events <!-- Fill timing: Phase 2-3; draft during design, finalized during spec writing -->
+## Domain Events <!-- Fill timing: Activity 2-3; draft during Domain Modeling, finalized during Spec Writing -->
 
 | Event | Trigger | Handler | Sync / Async |
 |---|---|---|---|
 | {EventName} | {何時觸發} | {Handler} | 同步/異步 |
 
-## Implementation Plan (Layer by Layer) <!-- Fill timing: Phase 4 -->
+## Implementation Plan (Layer by Layer) <!-- Fill timing: Activity 4: Implementation Planning -->
 
 ### Domain Layer
 > Aggregate 設計、Value Objects、Events、Interfaces
@@ -148,13 +151,13 @@ And {產生的 Domain Event}
 ### Presentation Layer
 > API Endpoint 設計、Request/Response 模型
 
-## Data Structure Changes <!-- Fill timing: Phase 4 -->
+## Data Structure Changes <!-- Fill timing: Activity 4: Implementation Planning -->
 
 | Table | Column | Change Type | Description |
 |---|---|---|---|
 | {Table} | {Column} | 新增/修改/刪除 | |
 
-## Test Strategy <!-- Fill timing: Phase 4 -->
+## Test Strategy <!-- Fill timing: Activity 4: Implementation Planning -->
 
 ### Domain Unit Tests
 - [ ] {不變條件測試}
@@ -169,14 +172,14 @@ And {產生的 Domain Event}
 - [ ] {Repository 測試}
 
 <!-- dflow:section open-questions -->
-## Open Questions <!-- Fill timing: Phase 1-4 -->
+## Open Questions <!-- Fill timing: Activity 1-4; any time during planning -->
 
 - {尚未釐清的需求、規則、資料或實作問題}
 
 <!-- dflow:section implementation-tasks -->
-## Implementation Tasks <!-- Fill timing: generated by AI after Phase 4; all items should be checked at completion -->
+## Implementation Tasks <!-- Fill timing: generated by AI after Activity 4: Implementation Planning; all items should be checked at completion -->
 
-> AI 在 Phase 4 實作規劃完成後，根據「Implementation Plan (Layer by Layer)」產生的具體任務清單。
+> AI 在 Activity 4 (Implementation Planning) 完成後，根據「Implementation Plan (Layer by Layer)」產生的具體任務清單。
 > 格式：`[LAYER]-[NUMBER]: 任務描述`
 > 分類標籤（Greenfield track，對應 Clean Architecture 各層）：
 >   - `DOMAIN` — Aggregate、Entity、VO、Domain Event、Domain Service、Repository Interface