What problem does it solve? Designing or documenting one business process across services often leaves hidden gaps: issuer-less commands, missing failure paths, blind decisions, and unhandled external-system silence. This Skill applies Alberto Brandolini's Process Modeling level of Event Storming to expose those gaps as explicit hot spots before they reach code. ## Core Features & Use Cases - Full sticky-note grammar: Enforces the read model → actor → command → aggregate/external system → event → policy loop with strict color, shape, and timeline rules. - Completeness walks: Provides forward/backward walks, orphan checks, silence checks for external systems, and first-event/out-of-order checks to validate the model. - Remote board guidance: Covers swimlane and frame layouts for Miro, Mural, and FigJam, including Miro DSL shape and board-read truncation pitfalls. - Model-to-code mapping: Translates stickies directly into process managers, sagas, workflow code, projections, and follow-up tickets. - Use Case: When adding a cancellation flow that spans an external carrier API, model the process on a timeline, run the silence check on the pink system sticky, and turn each dark-red hot spot into a ticket before implementation. ## Quick Start Ask Claude to model the booking cancellation process end-to-end with process-level Event Storming, marking every unknown as a hot spot.
