Verified:GitHub

event-storming-explorer

Extract past-tense domain events and actors into an event timeline.

1|Updated Feb 12, 2026

Search Tags:#clustering #design-thinking #event-flow #event-storming #ddd-workshop #domain-subdomains #subdomain-candidates

Ready to run

npx skills add https://github.com/dev-goraebap/grimoire --skill event-storming-explorer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: event-storming-explorer
Source: https://github.com/dev-goraebap/grimoire/tree/main/ddd-workshop/skills/event-storming-explorer
Command: npx skills add https://github.com/dev-goraebap/grimoire --skill event-storming-explorer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event Storming sessions often generate extensive, noisy outputs. This skill distills those outputs into a clear set of subdomain candidates by extracting past-tense domain events and actors and building a cohesive event timeline for analysis.

Core Features & Use Cases

Generates a Big Picture Event Storming timeline from the input events and actors.
Clusters events to surface candidate subdomains for later classification.
Produces two artifacts, event-flow.md and subdomain-map.md, documenting the timeline and candidate clusters.

Quick Start

Run the event-storming-explorer step after the requirements-refiner to generate event-flow.md and subdomain-map.md.

Frequently Asked Questions about event-storming-explorer

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

FAQPage Schema

How do I extract domain subdomains from Event Storming outputs?▼

To extract domain subdomains from Event Storming, apply time-ordered clustering to past-tense domain events and actors. This process distills noisy Big Picture Event Storming sessions into clear subdomain candidates for subsequent classifiers.

What is the best way to build an event timeline from Big Picture Event Storming?▼

Building an event timeline from Big Picture Event Storming involves extracting past-tense domain events and actors, then ordering them chronologically. The timeline excludes policies, commands, and system names to focus purely on domain events.

Can I use event-storming-explorer to identify bounded contexts for DDD workshops?▼

Yes, you can identify bounded context candidates for DDD workshops by clustering time-ordered domain events. This surfaces subdomain candidates from your Event Storming data, preparing them for later classification stages.

Do I need to include commands and policies when clustering event flows?▼

No, you do not include commands, policies, or system names when clustering event flows. The process strictly isolates past-tense domain events and actors to ensure the subdomain map remains free of technical infrastructure noise.

What artifacts are generated when mapping event flows and subdomain candidates?▼

Mapping event flows and subdomain candidates generates two markdown artifacts: event-flow.md documenting the chronological event timeline, and subdomain-map.md detailing the clustered subdomain candidates extracted from the Event Storming session.