event-storming-advanced

# Event Storming Advanced Skill

## When to Use This Skill

Use this skill when:

- **Event Storming Advanced tasks** - Working on deep dive event storming beyond big picture
- **Planning or design** - Need guidance on Event Storming Advanced approaches
- **Best practices** - Want to follow established patterns and standards

## Overview

Conduct Event Storming sessions beyond big picture to process and design levels.

## MANDATORY: Documentation-First Approach

Before facilitating Event Storming:

1. **Invoke `docs-management` skill** for Event Storming patterns
2. **Verify methodology** via MCP servers (perplexity)
3. **Base guidance on Alberto Brandolini's methodology**

## Event Storming Levels

```text
Event Storming Progression:

LEVEL 1: BIG PICTURE
├── Purpose: Understand the whole domain
├── Participants: Everyone (business + tech)
├── Output: Domain overview, hotspots, bounded contexts
└── Duration: 2-4 hours

LEVEL 2: PROCESS LEVEL
├── Purpose: Detail specific business processes
├── Participants: Domain experts + analysts
├── Output: Detailed flows, policies, read models
└── Duration: 2-4 hours per process

LEVEL 3: DESIGN LEVEL
├── Purpose: Translate to software design
├── Participants: Developers + architects
├── Output: Aggregates, commands, event handlers
└── Duration: 2-4 hours per aggregate

LEVEL 4: SOFTWARE DESIGN
├── Purpose: Implementation details
├── Participants: Development team
├── Output: Code structure, APIs, schemas
└── Duration: Ongoing
```

## Sticky Note Colors

```text
Standard Event Storming Palette:

🟠 ORANGE: Domain Events
   - Things that happened
   - Past tense naming
   - Business-significant state changes

🟦 BLUE: Commands
   - User intentions
   - Imperative naming
   - May be rejected

🟨 YELLOW: Actors/Users
   - Who initiates commands
   - Personas or roles
   - External systems

🟪 PURPLE/PINK: Policies/Reactions
   - Business rules
   - "When X happens, we do Y"
   - Automated responses

🟩 GREEN: Read Models
   - Info