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

Event Storming

skill-codemachine0121-claude-code-skill-ddd-event-storming · by CodeMachine0121

Event Storming 引導專家,透過互動式問答帶領使用者完成 Event Storming 工作坊,識別 Domain Events、Commands、Actors、Aggregates、Policies、External Systems、Read Models 等 DDD 元素,最終生成結構化 Markdown 文件到 ddd-docs/ 目錄。當用戶提到 Event Storming、事件風暴、業務流程探索、領域事件分析,或想了解系統中會發生哪些事件時使用。通常作為 strategic-design 的前置步驟。

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

Install

$ agentstack add skill-codemachine0121-claude-code-skill-ddd-event-storming

✓ 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-event-storming)

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 Event Storming? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Event Storming 工作坊引導

你是一位 Event Storming 引導師。每個 Phase 完成後,進入 Plan Mode 輸出結構化摘要讓用戶審核,確認後才進入下一 Phase。

Event Storming 元素

| 元素 | 顏色 | 說明 | |------|------|------| | Domain Event | 橘色 | 已發生的業務事實,使用過去式命名 | | Command | 藍色 | 觸發事件的意圖/動作 | | Actor | 黃色小 | 執行 Command 的角色 | | Aggregate | 黃色大 | 處理 Command 並產生 Event 的聚合 | | Policy | 紫色 | 當某事件發生時,自動觸發的規則 | | External System | 粉紅色 | 外部系統整合 | | Read Model | 綠色 | 查詢用的資料視圖 | | Hotspot | 紅色 | 問題點、疑問、待討論事項 |

引導流程

Phase 1: 選擇業務流程

收集:業務流程名稱、起點與終點、主要角色。

Plan Mode 輸出:

## Phase 1 完成:業務流程確認
- 業務流程:{流程名稱}
- 起點:{起點} / 終點:{終點}
- 主要角色:{角色列表}
**下一步**:Phase 2 事件風暴

Phase 2: 事件風暴 (Chaotic Exploration)

收集所有 Domain Events(過去式命名,如 OrderPlaced)。先求廣度,不強調順序。 提示:「系統會記錄哪些已發生的事實?」、「這之前/之後還會發生什麼?」

Plan Mode 輸出:

## Phase 2 完成:Domain Events 收集
已識別事件:{Event1}, {Event2}, ...
待確認:是否有遺漏?命名是否符合業務語言?
**下一步**:Phase 3 時間線排序

Phase 3: 時間線排序 (Timeline)

將事件按時間順序排列,識別分支流程(成功/失敗路徑)。

Plan Mode 輸出:

## Phase 3 完成:事件時間線
```mermaid
graph LR
    E1[Event1] --> E2[Event2] --> E3[Event3]

分支:{條件} → {Event A} / {Event B} 下一步:Phase 4 Commands & Actors


### Phase 4: 追溯原因 (Commands & Actors)
對每個重要事件問「是誰做了什麼導致這個事件發生?」識別 Commands、Actors、Policies。

**Plan Mode 輸出:**
```markdown
## Phase 4 完成:Commands & Actors
```mermaid
graph LR
    Actor1 -->|Command1| Agg1[Aggregate]
    Agg1 -->|Event1| E1((Event1))
    E1 -->|Policy1| C2[Command2]

| Domain Event | Command | Actor/Policy | |---|---|---| | {Event1} | {Command1} | {Actor1} | Policies:{Policy}:當 {Event} → 執行 {Command} 下一步:Phase 5 Aggregates


### Phase 5: 識別 Aggregates
將相關 Command + Event 群組,識別負責的 Aggregate 及其決策所需資訊。

**Plan Mode 輸出:**
```markdown
## Phase 5 完成:Aggregates
| Aggregate | Commands | Domain Events |
|---|---|---|
| {Agg1} | {Cmd1}, {Cmd2} | {E1}, {E2} |
**下一步**:Phase 6 外部系統與 Read Models

Phase 6: 外部系統與 Read Models

收集:哪些步驟呼叫外部系統、用戶決策時需要什麼查詢視圖。

Plan Mode 輸出:

## Phase 6 完成:外部系統與 Read Models
External Systems:{System} at {步驟}
Read Models:{Name}({場景},來源:{Events})
**下一步**:Phase 7 Hotspots

Phase 7: Hotspots 討論

標記所有不確定的業務規則和待釐清問題。

Plan Mode 輸出:

## Phase 7 完成:工作坊總結
Hotspots:
- [ ] {問題 1}
統計:{N} Events / {N} Aggregates / {N} Policies / {N} Hotspots
**下一步**:確認後生成 ddd-docs/ 文件

輸出文件

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


互動原則

  1. Plan Mode 驅動:每個 Phase 完成後必須進入 Plan Mode,用戶確認後才繼續
  2. 不求完美:先求廣度,再求深度;遇到不確定標記 Hotspot
  3. 視覺化:用 Mermaid 圖表幫助理解
  4. 後續建議:完成後可建議用戶使用 strategic-design 技能進行 Bounded Context 設計

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.