nw-ddd-event-modeling

Featured

Event Modeling facilitation technique — brainstorm events, identify commands and views, define aggregate boundaries, write Given-When-Then specifications

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Event Modeling Collaborative visual design technique created by Adam Dymitruk. The Event Model IS the specification -- it replaces traditional requirements documents with a single, living visual artifact. ## Key Properties - **Collaborative**: Everyone participates (devs, business, UX) - **Visual**: Colored elements on a timeline (physical or digital board) - **Timeline-based**: Events arranged chronologically, left to right - **Spec-generating**: Model directly produces testable Given/When/Then specifications - **Technology-agnostic**: Describes WHAT happens, not HOW it's implemented ## The Color System | Color | Element | Description | Example | |-------|---------|-------------|---------| | Orange | **Event** | Something that happened (past tense) | OrderPlaced, PaymentReceived | | Blue | **Command** | User intent/action (imperative) | PlaceOrder, ProcessPayment | | Green | **Read Model/View** | Data displayed to user | Order Summary, Shipping Dashboard | | White | **Screen/UI** | User interface wireframe | Order Form, Checkout Page | | Yellow | **Automation/Policy** | System reaction (saga/process manager) | "When PaymentReceived, then ConfirmOrder" | | Red | **External System** | Integration point | Payment Gateway, Email Service | ## Four Phases ### Phase 1: Event Brainstorming (10-20 min) Discover all meaningful things that happen in the system. **Process**: Everyone writes events on orange stickies (past tense, domain language) | Place on timeline (left = ea...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

designing-event-models

Designs and reviews Event Models — the visual blueprint for information systems using events, commands, read models, and screens. Produces structured YAML artifacts (swimlanes, slices, events, commands, read models, Given/When/Then specifications). Use when designing a new system or feature with Event Modeling, reviewing an existing event model for anti-patterns or completeness gaps, defining slices and GWT scenarios, or creating an event model from a system description.

0 Updated 2 days ago
msewell
Data & Documents Listed

event-storming

Use this skill whenever the user wants to create, document, or model an Event Storming. Triggers include: "do event storming", "model a domain", "map domain flow", "create an event diagram", "document bounded contexts", "model commands and events", "DDD", "Domain-Driven Design", "convert sticky notes into code", "represent flows with Mermaid", "create aggregates", "identify bounded contexts", "map domain policies". Also use this skill when the user provides business process descriptions and wants to transform them into structured Event Storming artifacts — even if they do not explicitly mention the term.

3 Updated today
Ronnasayd
AI & Automation Listed

domain-modeling

Discover and refine ubiquitous language, business rules, invariants, ownership, bounded contexts, and justified domain patterns. Use for domain-rich features, conflicting terminology, unclear consistency boundaries, legacy model extraction, or explicit DDD requests; skip simple CRUD, utilities, styling, and generic architecture cleanup.

8 Updated today
dayfinggg