Event Storm Command

Run an AI-simulated event storming workshop to discover domain events, commands, actors, and bounded contexts.

Arguments

• <domain-description>: Description of the domain, business process, or application to analyze

• --mode: Workshop mode (default: guided)

  • full: 5 persona agents debate in parallel, comprehensive discovery (~15K tokens)
  • quick: Single analysis pass, no personas (~3K tokens)
  • guided: Interactive with user, personas on-demand (variable)

• --dir: Output directory (default: docs/event-storming/)

Execution

Step 1: Parse Arguments

Extract the domain description and mode from the arguments.

If no domain description provided, ask the user: "What domain, business process, or application would you like to event storm?"

Default mode is guided unless specified.

Step 2: Load Event Storming Skill

Invoke the event-storming skill to access workshop methodology, sticky note conventions, and phase orchestration guidance.

Step 3: Execute Based on Mode

Full Mode (5 Personas in Parallel)

Launch 5 persona agents simultaneously to simulate workshop dynamics:

1. domain-expert: Contributes deep business knowledge, domain events, business rules, edge cases
2. developer-persona: Contributes technical events, integration points, system constraints
3. business-analyst: Contributes process flow, commands, actors, acceptance criteria
4. product-owner: Contributes priorities, MVP scope, user value assessment
5. devils-advocate: Challenges assumptions, identifies gaps, contradictions, missing scenarios

Each agent receives the same domain context and returns their perspective.

After all agents complete, synthesize their outputs:

• Merge event catalogs with provenance tracking ([persona] attribution)
• Identify hot spots where personas disagree
• Order events chronologically
• Group into bounded context candidates

Quick Mode (Single Pass)

Perform a rapid analysis without persona agents:

1. Identify obvious domain events (past tense, business-significant)
2. Map commands that trigger events
3. Identify actors who issue commands
4. Note potential bounded context boundaries
5. Flag areas needing deeper exploration

Output a concise event catalog.

Guided Mode (Interactive)

Work interactively with the user through 6 phases:

1. Chaotic Exploration: Ask user to brainstorm events freely
2. Timeline Ordering: Help order events chronologically
3. Command Discovery: For each event, ask "What triggers this?"
4. Actor Identification: For each command, ask "Who issues this?"
5. Bounded Context Discovery: Suggest groupings based on language/ownership
6. Hot Spot Resolution: Identify and discuss unclear areas

Offer to spawn specific persona agents for deeper analysis on hot spots.

Step 4: Generate Output Artifacts

Create the following outputs:

Event Catalog

# Event Storm Results: [Domain Name]

**Date:** [ISO Date]
**Mode:** [full|quick|guided]
**Participants:** [Personas used or "Interactive"]

## Domain Events

| Event | Triggered By | Actor | Context | Provenance |
|-------|--------------|-------|---------|------------|
| OrderPlaced | PlaceOrder | Customer | Orders | [domain-expert] |
| PaymentReceived | ProcessPayment | PaymentGateway | Payments | [developer-persona] |

## Commands

| Command | Actor | Triggers | Context |
|---------|-------|----------|---------|
| PlaceOrder | Customer | OrderPlaced | Orders |

## Bounded Context Candidates

### Orders Context
- Events: OrderPlaced, OrderShipped, OrderDelivered
- Commands: PlaceOrder, ShipOrder
- Actors: Customer, WarehouseStaff

### Payments Context
- Events: PaymentReceived, PaymentFailed, RefundIssued
- Commands: ProcessPayment, IssueRefund
- Actors: PaymentGateway, FinanceTeam

## Hot Spots (Needs Discussion)

- [ ] Where does inventory check happen?
- [ ] Who handles partial shipments?

Integration Suggestions

After completing the event storm, suggest:

• Domain storytelling sessions for unclear processes
• Architecture documentation using discovered contexts
• ADRs for key decisions made during the session

Step 5: Save Results

If the user wants to save results, write the event catalog to:

• docs/event-storming/[domain-name]-[date].md Use --dir for custom location.
• Or ask user for preferred location