event-storming

Facilitate Event Storming workshops to discover domain events, bounded contexts, and aggregates.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/vnovakovits/claude-skills --skill event-storming-vnovakovits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: event-storming
Source: https://github.com/vnovakovits/claude-skills/tree/main/plugins/engineering-practices/skills/event-storming
Command: npx skills add https://github.com/vnovakovits/claude-skills --skill event-storming-vnovakovits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams starting new systems or exploring complex domains often build models in isolation, missing knowledge that lives across business, product, and engineering stakeholders. This Skill guides collaborative Event Storming workshops that surface domain events, bounded contexts, and hidden assumptions in hours rather than weeks. ## Core Features & Use Cases - Three Workshop Levels: Covers Big Picture (whole-domain discovery), Process Modeling (single-process detail), and Software Design (aggregates and tactical design) sessions. - Sticky-Note Grammar: Defines the color-coded notation — orange domain events, blue commands, yellow actors and aggregates, pink external systems, green read models, lilac policies, and red hot spots. - Facilitation Guidance: Provides the full workshop flow from chaotic exploration through timeline enforcement to bounded-context identification, plus facilitation tips and common mistakes. - Use Case: Before designing a new reservation system, run a Big Picture workshop with domain experts and developers to map events like "Reservation Confirmed" and "Payment Received", then draw bounded-context boundaries that inform service decomposition. ## Quick Start Ask Claude to help plan and facilitate an Event Storming workshop for your domain, including the sticky-note grammar, session flow, and how to translate the results into DDD building blocks.

Frequently Asked Questions about event-storming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an Event Storming workshop?▼

Start with chaotic exploration where everyone writes past-tense domain events on orange stickies, then enforce a timeline, mark hot spots, add actors and external systems, and walk the model. Later sessions add commands, aggregates, policies, and read models before drawing bounded-context boundaries.

What do the sticky note colors mean in Event Storming?▼

Orange marks domain events, blue marks commands, small yellow marks actors, pink marks external systems, green marks read models, lilac marks policies, large yellow marks aggregates, and red or angled notes mark hot spots. The colors are conventions; the meaning behind each note is what matters.

How does Event Storming relate to Domain-Driven Design?▼

Event Storming is the discovery technique that produces DDD artifacts: wall boundaries become bounded contexts, event clusters become aggregates, orange stickies become domain events, and lilac policies become sagas or process managers. Running workshops first prevents inventing models in isolation.

Can Event Storming be done remotely?▼

Yes, tools like Miro, Mural, or FigJam support virtual Event Storming when in-person sessions are not possible. Energy and bandwidth are lower, so use breakout rooms for chaotic exploration and bring everyone together for timeline walkthroughs.

When should you not use Event Storming?▼

Avoid it for trivial CRUD systems with no emergent complexity, one-person teams where collaboration adds no value, situations where domain experts are unavailable, or well-known domains under strict time constraints where the model is already understood.