What problem does it solve? Teams starting domain-driven design often lack a shared understanding of what actually happens inside a business domain, leading to misaligned terminology, missed edge cases, and poorly drawn context boundaries. This Skill structures collaborative domain discovery so events, commands, and hotspots are captured systematically before any modeling begins. ## Core Features & Use Cases - Event Storming Workflow: Enumerates past-tense domain events, completes their triggering commands, and arranges them on a timeline covering at least one main path plus two exception paths. - Hotspot and Ambiguity Capture: Flags consistency, integration, performance, and compliance hotspots, and records terminology conflicts with the party responsible for confirming each. - Boundary Clue Output: Produces preliminary capability groupings and candidate context boundaries that feed directly into downstream subdomain decomposition. - Use Case: Given a scoped problem like a chaotic order after-sales process, run discovery to produce an event flow table, command/event candidate lists, hotspot annotations, and an ambiguity list before defining bounded contexts. ## Quick Start Ask the assistant to run ddd-discover on your business scenario or ddd-scope output to produce the event flow table, command and event candidates, hotspot annotations, and ambiguity list.
