Stats
Actions
Available In
Tags
Plugin
trogonstack-eventmodeling
Event Modeling skills for brainstorming, designing, slicing, and validating software systems following the Event Modeling methodology
What's Inside
Skills16
eventmodeling-applying-conways-law
/eventmodeling-applying-conways-law
Step 6 of Event Modeling - Apply Conway's Law with swimlanes. Organize events into autonomous system parts that different teams can independently own. Use after defining inputs/outputs. Do not use for: planning feature slice implementation order (use eventmodeling-slicing-event-models) or defining command/read model boundaries (use eventmodeling-designing-event-models).
eventmodeling-brainstorming-events
/eventmodeling-brainstorming-events
Step 1 of Event Modeling - Brainstorm all domain events from requirements. Extract every state-changing event the system could have. Use when starting event modeling from requirements or a new domain. Do not use for: arranging events in sequence (use eventmodeling-plotting-events), designing commands or read models (use eventmodeling-designing-event-models), or when a complete event list already exists.
eventmodeling-checking-completeness
/eventmodeling-checking-completeness
Step 8 of Event Modeling - Completeness Check. Verify every field has origin and destination. Ensure complete event model before code generation. Use after all scenarios defined. Do not use for: architectural validation against event sourcing principles (use eventmodeling-validating-event-models) or elaborating Given-When-Then specs (use eventmodeling-elaborating-scenarios).
eventmodeling-designing-event-models
/eventmodeling-designing-event-models
Designs event-sourced domain models. Maps business processes to immutable events and state projections. Events are the source of truth; state is derived from events for command validation. Use when designing event streaming architectures from domain analysis. Do not use for: brainstorming events from scratch (use eventmodeling-brainstorming-events), optimizing stream sizing or snapshotting (use eventmodeling-optimizing-stream-design), or translating external system events (use eventmodeling-translating-external-events).
eventmodeling-elaborating-scenarios
/eventmodeling-elaborating-scenarios
Step 7 of Event Modeling - Elaborate scenarios using Given-When-Then format. Specify behavior of commands and views. Each spec tied to exactly one command or view. Use after defining systems and boundaries. Do not use for: architectural validation (use eventmodeling-validating-event-models) or verifying field completeness across the model (use eventmodeling-checking-completeness).
Stats
Version0.1.0
Released
Stars0
MaintenanceFair
LicenseMIT
Last Commit
Added
Available In
Tags
Categories
