What problem does it solve? Designing event-driven systems requires translating vague business requirements into concrete domain events, commands, and views, which is error-prone and often skips stakeholder validation. This Skill guides a structured event modeling process that discovers business processes, identifies domain events in chronological order, and iterates with user approval at every stage. ## Core Features & Use Cases - Dual Input Modes: Model from text-based domain requirements or reverse-engineer an existing codebase by exploring event definitions, command handlers, and aggregates. - Gated Multi-Phase Workflow: Eight phases covering capability identification, storyboarding, event timeline discovery, anti-pattern checks, autonomous component grouping, and message processing pattern labeling, each requiring explicit user approval. - Documented Outputs: Produces a complete event model Markdown document and a Draw.io diagram with swimlanes, timelines, and styled elements saved under docs/. - Use Case: Given requirements for an order fulfillment system, the Skill asks clarifying questions, derives processes like Order Booking and Payment, identifies events such as OrderPlaced and PaymentSucceeded, and delivers an implementable event model with component boundaries. ## Quick Start Ask the AI to perform event modeling on your domain requirements or point it at a codebase path, for example by requesting an event model for your order processing workflow.
