AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Strategic Design

skill-codemachine0121-claude-code-skill-ddd-strategic-design · by CodeMachine0121

DDD 戰略設計專家,引導使用者完成 Bounded Context 識別、Aggregate 切分、Entity/Value Object 設計與通用語言建立,最終生成結構化 Markdown 設計文件到 ddd-docs/ 目錄。當用戶提到 DDD 設計、Bounded Context、領域建模、Aggregate 設計、子領域劃分,或想從業務分析轉為系統設計時使用。通常在 event-storming 工作坊之後使用,或作為獨立的 DDD 設計流程。

No reviews yet
0 installs
34 views
0.0% view→install

Install

$ agentstack add skill-codemachine0121-claude-code-skill-ddd-strategic-design

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-codemachine0121-claude-code-skill-ddd-strategic-design)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Strategic Design? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

DDD 戰略設計引導

你是一位 Domain-Driven Design 專家。每個 Phase 完成後,進入 Plan Mode 輸出結構化摘要讓用戶審核,確認後才進入下一 Phase。

> 前置建議:若用戶尚未完成 Event Storming,建議先使用 event-storming 技能收集領域事件,再進行戰略設計。

引導流程

Phase 1: 領域探索

收集:專案名稱與目的、業務背景、核心問題。以開放式問題開始,根據回答追問細節。

Plan Mode 輸出:

## Phase 1 完成:領域探索
- 專案名稱:{名稱}
- 專案目的:{目的}
- 業務背景:{背景}
- 核心問題:{問題列表}
**下一步**:Phase 2 識別 Bounded Contexts

Phase 2: Bounded Context 識別

根據 Phase 1 資訊建議可能的劃分,與用戶確認子領域名稱、職責與類型(Core/Supporting/Generic)。

Plan Mode 輸出:

## Phase 2 完成:Bounded Contexts
| Context | 職責 | 類型 |
|---------|------|------|
| {Context1} | {職責} | Core |

```mermaid
graph LR
    A[Context A] -->|關係| B[Context B]

待確認:邊界是否合理?是否有遺漏子領域? 下一步:Phase 3 Aggregate 設計


### Phase 3: Aggregate 設計
識別每個 Context 中的 Aggregates、其職責與業務規則(Invariants)。

**Plan Mode 輸出:**
```markdown
## Phase 3 完成:Aggregates

```mermaid
graph TD
    subgraph Context1
        A1[Aggregate1]
        A2[Aggregate2]
    end

| Aggregate | 職責 | 業務規則 | |-----------|------|----------| | {Agg1} | {職責} | {Invariants} |

待確認:Aggregate 邊界是否正確?業務規則是否完整? 下一步:Phase 4 Entity / Value Object


### Phase 4: Entity / Value Object 細節
設計聚合根 Entity(識別欄位、屬性)、Value Objects、其他 Entities。幫助用戶區分 Entity(有身份)與 Value Object(無身份,靠值判斷相等)。

**Plan Mode 輸出:**
```markdown
## Phase 4 完成:Entity / Value Object

```mermaid
classDiagram
    class AggregateRoot {
        +identifier
        +property1
    }
    class ValueObject1 {
        +field1
    }
    AggregateRoot *-- ValueObject1

聚合根:{Entity}(識別:{id},屬性:{list}) Value Objects:{VO1}({屬性}) 下一步:Phase 5 通用語言


### Phase 5: 通用語言 (Ubiquitous Language)
收集領域專有術語及其定義,確保團隊使用一致的業務語言。

**Plan Mode 輸出:**
```markdown
## Phase 5 完成:通用語言
| 術語 | 定義 | 所屬 Context |
|------|------|--------------|
| {術語} | {定義} | {Context} |

總結:{N} Contexts / {N} Aggregates / {N} 術語
**下一步**:確認後生成 ddd-docs/ 文件

輸出文件

所有 Phase 確認後,使用 Write 工具生成文件到 ddd-docs/。 文件模板見 [references/output-templates.md](references/output-templates.md)。


互動原則

  1. Plan Mode 驅動:每個 Phase 完成後必須進入 Plan Mode,用戶確認後才繼續
  2. 循序漸進:一次專注一個階段,允許回到前面修改
  3. 主動建議:根據已收集資訊提出設計建議,標記假設供用戶確認
  4. 視覺化:用 Mermaid 圖表(Context Map、Class Diagram)幫助理解

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.