English version: English
When to use
- Need to quickly align core business processes with domain boundary clues.
- Requirements are already clear (from
ddd-scopeor directly provided by the user), and it is necessary to explore what happens inside the domain. ddd-contextsWhen the report says "terminology conflicts are irreconcilable," re-execute as a backtracking target.
Input requirements
- Required: business scenario description (user stories, PRD, tickets, or the output of
ddd-scopeare all acceptable). - Optional: key participants and external systems, business constraints and non-goals (from
ddd-scope)。
Process
- List events: from the perspective of "facts that have already occurred," usepast tenseto name domain events (such as OrderPlaced, PaymentReceived).
- Complete commands: for each event, supplement the command that triggers it, the initiator, and key input data.
- Arrange chronology: organize events along a timeline, identify branches, rollbacks, and exception paths (cover at least 1 main path + 2 exception paths).
- Mark hotspots: mark high-frequency events, strong consistency points, cross-system boundaries, performance-sensitive points, and compliance checkpoints.
- Generate ambiguity list: record terminology conflicts, unclear states, and ambiguous ownership issues, and mark "who must confirm."
- Output boundary clues: extract preliminary capability groupings and context boundary candidates from event clustering and hotspot distribution.
Output
| Artifacts | Structural requirements |
|---|---|
| Event flow table | Table: sequence number, event name (past tense), triggering command, participants, input/output, exception branches |
| Command candidate list | Table: command, initiator, expected result, idempotency requirement |
| Event candidate list | Table: event, key fields, whether cross-context, whether externally published |
| Hotspot annotations | List: consistency hotspots, integration hotspots, performance hotspots, compliance hotspots |
| Ambiguity list | Table: ambiguity point, impact scope, confirmer, recommended decision |
| Boundary clues | List: preliminary capability groupings and potential context boundaries |
Checklist
- Events are named in the past tense and are understandable to the business
- Covers at least 1 main path + 2 exception/rollback paths
- Hotspots clearly mark cross-system boundaries and strong consistency points
- Each item in the ambiguity list marks "who must confirm"
- Boundary clues can be directly consumed by
ddd-subdomainsdirect consumption
Backtracking trigger
- This Skill is triggered for backtracking by
ddd-contexts: when > 5 terms have irreconcilable cross-context conflicts, it indicates insufficient domain understanding and requires rediscovery.
Example
@ddd-discover
基于以下 scope 输出,帮我做领域发现:
- 问题:订单售后流程混乱
- 目标:支持退款、换货、投诉处理
- 非目标:不涉及正向下单流程
请输出事件流表、命令/事件候选、热点标注与歧义清单。