dflow-sdd-ddd 0.1.0

package/templates/webforms/templates/lightweight-spec.md

@@ -0,0 +1,82 @@
+---
+id: BUG-{NUMBER}
+title: {簡述問題}
+status: in-progress
+bounded-context: {ContextName}
+created: {YYYY-MM-DD}
+branch: bugfix/BUG-{NUMBER}-{short-description}
+---
+
+<!--
+Template note (for AI):
+  This is the **lightweight-spec** template — it corresponds to T2 Light
+  ceremony in the three-tier Ceremony Scaling (T1 Heavy / T2 Light /
+  T3 Trivial; see SKILL.md § Ceremony Scaling for the tier criteria).
+
+  - T1 Heavy → use templates/phase-spec.md instead
+  - T2 Light → THIS template; produces an independent file
+  - T3 Trivial → no independent file; just one inline row in _index.md
+                 Lightweight Changes with a tag like [cosmetic] / [text] / [format]
+
+  Instance file location and naming:
+    Place the instantiated file inside the corresponding feature directory:
+      dflow/specs/features/active/{SPEC-ID}-{slug}/lightweight-{YYYY-MM-DD}-{slug}.md
+    or, when the lightweight change is a tracked bug:
+      dflow/specs/features/active/{SPEC-ID}-{slug}/BUG-{NUMBER}-{slug}.md
+
+    If the change is a standalone bug not yet attached to any existing
+    feature, /dflow:bug-fix must first create a feature directory (with a
+    minimal _index.md) before placing the lightweight-spec instance inside.
+    This keeps the structure invariant: every spec file lives under some
+    feature directory.
+
+  After finalizing this lightweight-spec, AI must:
+    1. Add an outbound-link row to the feature's _index.md Lightweight Changes table
+       (Tier = T2; description includes the link to this file)
+    2. Refresh the feature's _index.md Current BR Snapshot table to reflect
+       any BR ADDED / MODIFIED / REMOVED / RENAMED in this lightweight-spec
+-->
+
+# {問題簡述}
+
+## Problem
+
+{什麼東西壞了？或什麼行為不正確？}
+
+## Behavior Delta
+
+> 精簡 delta 格式：bug fix 多數只需 MODIFIED；若確實是新增規則可改用 ADDED、移除用 REMOVED、改名用 RENAMED。多項變更時照類別列。
+
+### MODIFIED - behavior modified in this fix
+#### Rule: BR-NN {規則名稱}
+**Before**: Given {current state} When {action} Then {current (incorrect) result}
+**After**: Given {same state} When {same action} Then {correct result}
+**Reason**: {why this change — bug / requirement clarification / spec alignment}
+
+<!-- 若需要 ADDED / REMOVED / RENAMED / UNCHANGED 請比照 references/modify-existing-flow.md 的 Delta 格式 -->
+
+
+## Root Cause
+
+{為什麼會這樣？是邏輯錯誤？資料問題？還是需求理解有誤？}
+
+## Fix Approach
+
+{怎麼修？有沒有抽到 Domain 層的機會？}
+
+<!-- dflow:section implementation-tasks -->
+## Implementation Tasks
+
+> Keep T2 Light tasks concise. If the fix scope starts to expand, AI should pause and ask the developer whether to keep this as T2 or upgrade it to T1. Do not auto-upgrade based on task count alone.
+>
+> Recommended layer tags (WebForms): `DOMAIN` / `PAGE` / `DATA` / `TEST` / `DOC`
+
+- [ ] {LAYER}-1: {minimal required change}
+- [ ] TEST-1: {minimal verification / regression test}
+- [ ] DOC-1: Update `_index.md` Lightweight Changes and Current BR Snapshot
+
+Layer tag list above is the recommended set; the developer may extend with project-specific tags as needed.
+
+## Tech Debt Discovered (if any)
+
+{在修這個 bug 時發現的其他問題，記錄到 tech-debt.md}

package/templates/webforms/templates/models.md

@@ -0,0 +1,39 @@
+<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+
+# Domain Models
+
+> Domain model catalog for one bounded context.
+
+## Context
+
+- **Bounded Context**: {Context name}
+- **Source Code Area**: `{project/path/or/namespace}`
+- **Last Updated**: {YYYY-MM-DD}
+
+## Entities
+
+| Entity | Responsibility | Key Identity | Code Mapping | Notes |
+|---|---|---|---|---|
+| {EntityName} | {核心職責} | {Id / composite key} | `{Namespace.Class}` | {optional notes} |
+
+## Value Objects
+
+| Value Object | Responsibility | Equality Components | Code Mapping | Notes |
+|---|---|---|---|---|
+| {ValueObjectName} | {代表的概念} | {fields} | `{Namespace.Class}` | {optional notes} |
+
+## Domain Services
+
+| Service | Responsibility | Inputs / Outputs | Code Mapping | Notes |
+|---|---|---|---|---|
+| {ServiceName} | {跨 entity/value object 的 domain operation} | {inputs -> outputs} | `{Namespace.Class}` | {optional notes} |
+
+## Repository Interfaces
+
+| Repository | Aggregate / Entity | Query Responsibility | Code Mapping | Notes |
+|---|---|---|---|---|
+| {RepositoryName} | {EntityName} | {查詢或保存責任} | `{Namespace.Interface}` | {optional notes} |
+
+## Code Mapping Notes
+
+- {domain concept} maps to `{existing WebForms / EF / service code}`.

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

@@ -0,0 +1,187 @@
+---
+id: {CONTEXT}-{NUMBER}
+title: Feature title
+status: draft | in-progress | completed
+bounded-context: {ContextName}
+created: {YYYY-MM-DD}
+author: {developer-name}
+branch: feature/{CONTEXT}-{NUMBER}-{short-description}
+---
+
+# {Feature Title}
+
+<!--
+Template note (for AI):
+  This is the **phase-spec** template - one phase-spec captures one full
+  "Kickoff -> Domain -> Design -> Build -> Verify" cycle inside a feature directory.
+  A feature can have 1..N phase-specs; the feature-level dashboard lives in
+  the sibling `_index.md` (see templates/_index.md). The instance file name is
+  `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 Analysis (Where does it live?)
+    Phase 3 - Spec Writing (Behavior + Rules + Edge Cases)
+    Phase 4 - Implementation Planning
+  The "Implementation Tasks" section at the end is generated by AI after Phase 4 planning is done
+  (see new-feature-flow.md Step 5 end / new-phase-flow.md Step 4 end /
+   modify-existing-flow.md Step 4 end).
+
+  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`
+  Current BR Snapshot table.
+-->
+
+## Problem Description <!-- Fill timing: Phase 1 -->
+
+這個功能要解決什麼問題？誰需要它？
+
+> 用使用者的角度描述，避免技術用語。
+
+## Domain Concepts <!-- Fill timing: Phase 2 -->
+
+涉及的 Domain 概念（引用 `dflow/specs/domain/{context}/models.md`）：
+
+| Concept | Type | Description |
+|---|---|---|
+| {ConceptName} | Entity / Value Object / Domain Service | 簡述角色 |
+
+如有新概念，先更新：
+- [ ] `dflow/specs/domain/glossary.md` — 新增術語
+- [ ] `dflow/specs/domain/{context}/models.md` — 新增模型定義
+
+<!-- dflow:section behavior-scenarios -->
+## Behavior Scenarios <!-- Fill timing: Phase 3 -->
+
+### Main Success Scenario
+
+```gherkin
+Scenario: {情境名稱}
+  Given {初始狀態}
+  When {使用者操作}
+  Then {預期結果}
+```
+
+### Alternative Scenarios
+
+```gherkin
+Scenario: {替代情境}
+  Given {不同初始狀態}
+  When {使用者操作}
+  Then {不同的預期結果}
+```
+
+## Business Rules <!-- Fill timing: Phase 3 -->
+
+> Phase 2+ 注意：本段僅列**本 phase 新增 / 修改到的 BR**；未變動的 BR 不重抄
+> （它們的當前狀態見 feature 的 `_index.md` Current BR Snapshot 表）。
+
+| BR-ID | Rule | Notes |
+|---|---|---|
+| BR-01 | {規則描述} | |
+| BR-02 | {規則描述} | |
+
+## Delta from prior phases <!-- Fill timing: Phase 3; skip for the first phase -->
+
+> 本段僅記**本 phase 相對前一 phase 的變化**，不累積歷史。歷史由 feature 目錄下
+> 各 phase-spec 的本段串接閱讀；feature 層的當前累積狀態見 `_index.md` 的
+> Current BR Snapshot。
+>
+> **首 phase**：標註「首 phase，無前置 Delta」即可，不需逐項填。
+> **Phase 2+**：必填；格式沿用 modify-existing-flow.md 的 Delta 規則
+> （ADDED / MODIFIED / REMOVED / RENAMED + 選用 UNCHANGED）。
+
+### ADDED - BR / behavior added in this phase
+#### Rule: BR-NN {規則名稱}
+Given {初始狀態}
+When {操作}
+Then {新的預期結果}
+
+### MODIFIED - BR / behavior modified in this phase
+#### Rule: BR-NN {規則名稱}
+**Before**: Given … When … Then {old result}
+**After**: Given … When … Then {new result}
+**Reason**: {why this change}
+
+### REMOVED - BR removed in this phase
+#### Rule: BR-NN {規則名稱}
+**Reason**: {why removed}
+
+### RENAMED - BR renamed in this phase
+#### Rule: {old name} -> {new name}
+**Reason**: {why renamed}
+
+### UNCHANGED - explicitly unaffected (optional)
+- BR-003 金額上限
+- BR-005 提交後不可修改
+
+## Edge Cases <!-- Fill timing: Phase 3 -->
+
+| ID | Case | Expected Handling |
+|---|---|---|
+| EC-01 | {邊界描述} | {處理方式} |
+| EC-02 | {邊界描述} | {處理方式} |
+
+## Implementation Notes <!-- Fill timing: Phase 4 -->
+
+### Current WebForms Implementation
+
+> 在現有架構下如何實作？哪些 Code-Behind 會被修改？
+
+### Domain Layer Design
+
+> 哪些邏輯放到 `src/Domain/{Context}/`？需要哪些 interface？
+
+```csharp
+// 關鍵 Domain 類別草稿
+```
+
+### Keep Code-Behind Thin
+
+> Code-Behind 只負責：解析 UI 輸入 -> 呼叫 Domain 層 -> 顯示結果
+
+### Future ASP.NET Core Migration Considerations
+
+> 遷移時需要注意的事項，或者現在的設計如何幫助未來遷移。
+
+## Data Structure Changes <!-- Fill timing: Phase 4 -->
+
+> 涉及的資料表與欄位變更（如有）
+
+| Table | Column | Change Type | Description |
+|---|---|---|---|
+| {Table} | {Column} | 新增/修改/刪除 | |
+
+## Test Strategy <!-- Fill timing: Phase 4 -->
+
+> Domain 層的單元測試應驗證哪些行為？
+
+- [ ] {測試案例 1}
+- [ ] {測試案例 2}
+
+<!-- dflow:section open-questions -->
+## Open Questions <!-- Fill timing: Phase 1-4 -->
+
+- {尚未釐清的需求、規則、資料或實作問題}
+
+<!-- dflow:section implementation-tasks -->
+## Implementation Tasks <!-- Fill timing: generated by AI after Phase 4; all items should be checked at completion -->
+
+> AI 在 Phase 4 實作規劃完成後，根據「Implementation Notes」產生的具體任務清單。
+> 格式：`[LAYER]-[NUMBER]: 任務描述`
+> 分類標籤（WebForms 版）：
+>   - `DOMAIN`  — Domain 層類別、VO、Service、Interface
+>   - `PAGE`    — Code-Behind / ASPX 變更
+>   - `DATA`    — 資料表 schema 或 Repository 實作
+>   - `TEST`    — 測試案例
+> 本段在 spec 歸檔（搬到 `completed/`）前應確認全部勾選，或明確標註未完成項的 follow-up。
+
+- [ ] DOMAIN-1: {任務描述}
+- [ ] DOMAIN-2: {任務描述}
+- [ ] PAGE-1: {任務描述}
+- [ ] DATA-1: {任務描述}
+- [ ] TEST-1: {任務描述}

package/templates/webforms/templates/rules.md

@@ -0,0 +1,24 @@
+<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+
+# Business Rules
+
+> Declarative BR-ID index for one bounded context.
+
+<!-- dflow:section business-rules -->
+## Rule Index
+
+| BR-ID | Rule summary | Behavior anchor | Status | Last updated |
+|---|---|---|---|---|
+| BR-001 | {業務規則摘要} | [BR-001](./behavior.md#br-001-rule-name) | draft | {YYYY-MM-DD} |
+
+## Status Legend
+
+| Status | Meaning |
+|---|---|
+| draft | Rule is identified but not fully validated. |
+| active | Rule is validated and expected to be enforced. |
+| deprecated | Rule is retained for history but no longer active. |
+
+## Open Questions
+
+- {需要 domain expert 確認的規則}

package/templates/webforms/templates/tech-debt.md

@@ -0,0 +1,15 @@
+<!-- Template maintained by Dflow. See proposals/PROPOSAL-013 for origin. -->
+
+# Migration Tech Debt
+
+> WebForms migration debt backlog discovered during SDD/DDD work.
+
+## Debt Items
+
+| Item | Location | Description | Severity | Migration impact | Status |
+|---|---|---|---|---|---|
+| {Debt item} | `{file/path/or/namespace}` | {問題描述} | {Low/Medium/High/Critical} | {對 WebForms -> Core 遷移的影響} | {open/planned/in-progress/done} |
+
+## Follow-up Notes
+
+- {需要後續 proposal、refactor 或 migration plan 的事項}