event-model-plan

Design event models and write Event Models using emlang notation.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/sparkle-space/event-modeler --skill event-model-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-model-plan
Source: https://github.com/sparkle-space/event-modeler/tree/main/.claude/skills/event-model-plan
Command: npx skills add https://github.com/sparkle-space/event-modeler --skill event-model-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill assists users in designing event models and writing Event Models according to the Event Modeling methodology and a defined format, streamlining the process of information system design.

Core Features & Use Cases

  • Event Modeling Guidance: Provides a step-by-step guide for the 7-step Event Modeling workshop.
  • Slice Definition: Enables the definition of work units using emlang notation for triggers, commands, events, and views.
  • Event Model Formatting: Outlines the structure, event stream format, and key rules for creating Event Model files.
  • Use Case: A software architect needs to design a new feature. They can use this Skill to guide them through brainstorming domain events, defining commands and views, and structuring the final Event Model documentation.

Quick Start

Use the event-model-plan skill to help define a slice for user registration, including command, event, and view.

Frequently Asked Questions about event-model-plan

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

FAQPage Schema
What is event modeling and how does it structure system design?

Event modeling is a methodology for designing information systems by documenting event-driven processes. It structures system design through a 7-step workshop to define triggers, commands, events, and views.

How do I write an Event Model file using emlang notation?

To write an Event Model file, use emlang notation to define work slices including triggers, commands, events, and views, following the specific markdown format and event stream structure rules provided by the event-model-plan methodology.

How to define a work slice for user registration in event modeling?

To define a work slice for user registration, identify the specific trigger, command, event, and view involved in the registration process, and document them using emlang notation within the Event Model file structure.

Does event modeling work with domain-driven design and software architecture documentation?

Yes, event modeling aligns with domain-driven design and software architecture documentation by providing a structured, event-driven approach to capture domain events and system workflows clearly.

What are the limitations of using emlang for event storming?

The metadata does not specify explicit limitations of using emlang for event storming, but it is primarily designed to define event modeling slices and structure event stream data rather than general unrestricted brainstorming.