domain-event-modeling

What problem does it solve?

This Skill helps you define domain events as durable, self-describing past-tense facts so asynchronous consumers can reliably reconstruct what happened without querying mutable state.

Core Features & Use Cases

• Durable event contracts: Specifies required identifiers, payload facts, schema versioning, and compatibility rules so producers and consumers stay aligned.
• Reliable publication and safety: Enforces post-commit publishing via an outbox pattern, consumer idempotency requirements, and explicit retry/DLQ handling.
• Operational clarity: Documents ordering expectations, dead-letter strategy ownership, and audit/privacy impact so failures and governance are manageable.

Quick Start

Use the domain-event-modeling guidance to define a new event like OrderPlaced as a past-tense fact with an explicit outbox commit boundary, idempotency key, schemaVersion, retry/DLQ policy, and privacy-safe payload fields.