Run AI-simulated event storming workshop. Modes - full (5 personas), quick (single pass), guided (interactive). Discovers domain events, commands, actors, bounded contexts.
Facilitates AI-simulated event storming workshops to discover domain events, commands, actors, and bounded contexts.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install soft-skills@melodic-software<domain-description> [--mode full|quick|guided] [--dir <path>]Run an AI-simulated event storming workshop to discover domain events, commands, actors, and bounded contexts.
<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/)
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.
Invoke the event-storming skill to access workshop methodology, sticky note conventions, and phase orchestration guidance.
Launch 5 persona agents simultaneously to simulate workshop dynamics:
Each agent receives the same domain context and returns their perspective.
After all agents complete, synthesize their outputs:
Perform a rapid analysis without persona agents:
Output a concise event catalog.
Work interactively with the user through 6 phases:
Offer to spawn specific persona agents for deeper analysis on hot spots.
Create the following outputs:
# 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?
After completing the event storm, suggest:
If the user wants to save results, write the event catalog to:
docs/event-storming/[domain-name]-[date].md Use --dir for custom location.