event-storming

Analyze code to produce Event Storming documentation with per-BC Markdown files.

41|7|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/DGouron/review-flow --skill event-storming-dgouron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-storming
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/event-storming
Command: npx skills add https://github.com/DGouron/review-flow --skill event-storming-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event Storming analysis helps teams map domain events, commands, entities, and boundaries by exploring the codebase and producing a structured, strategic view of the system.

Core Features & Use Cases

  • Discovers domain events, commands, entities, and bounded contexts by scanning the repository structure.
  • Produces a per-BC Event Storming document and an aggregated big-picture view to guide domain conversation and design decisions.
  • Aligns with Vaughn Vernon patterns for context mapping and strategic design, enabling clear ubiquitous language across teams.

Quick Start

Execute /event-storming <bc-name> or /event-storming global to generate the Event Storming documentation.

Frequently Asked Questions about event-storming

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

FAQPage Schema
How do I generate Event Storming documentation from existing code?

Event Storming documentation is produced by analyzing your repository structure to discover domain events, commands, entities, and bounded contexts, outputting structured Markdown files for strategic domain analysis.

What is the best way to map bounded contexts in a Domain-Driven Design project?

Mapping bounded contexts involves applying Vaughn Vernon patterns to explore your codebase, generating a global big-picture view and per-BC Markdown documents to establish clear context boundaries.

Can I use this to create a big-picture view of my domain events?

Yes, creating a big-picture view is supported by running the global analysis command, which aggregates discovered domain events and commands into an overview Markdown file for domain conversation.

Does this Event Storming tool work without specific external dependencies?

Yes, the tool operates without external dependencies, but it requires direct access to your codebase to scan repository structures and identify Domain-Driven Design patterns effectively.

How do I document ubiquitous language across multiple teams?

Documenting ubiquitous language is achieved by aligning context mapping with Vaughn Vernon patterns, producing structured Event Storming documents that guide design decisions and establish clear terminology.