What problem does it solve?
This Skill prevents production incidents by helping you identify the full business-domain impact of a proposed change, including bounded-context boundaries, aggregates and invariants, domain events and consumers, ubiquitous language drift, and cross-context side effects.
Core Features & Use Cases
- Bounded-context impact mapping: Determine which bounded contexts are affected, how they relate (e.g., Published Language, Shared Kernel, Anti-Corruption Layer), and what coordination is required.
- Aggregate and invariant integrity review: Enumerate which aggregates are impacted and confirm invariants are enforced at the aggregate boundary, not only in application code.
- Domain event contract evolution: Analyze added, changed, deprecated, or versioned events, including consumer lists, migration strategy, and failure handling expectations.
- Ubiquitous language consistency audit: Detect term renames/redefinitions and map propagation risk across all affected contexts.
- Cross-domain side effects and delivery guarantees: Specify what downstream behaviors are triggered, including reliability expectations (e.g., outbox/event publishing patterns) and compensation approaches for multi-step processes.
- Risk escalation and team handoff: Provide explicit escalation triggers and recommend which ownership reviewers must acknowledge the impact.
Quick Start
Ask the domain-impact-modeler to produce a domain impact analysis for your proposed change by listing affected bounded contexts, impacted aggregates and invariants, event contract deltas with consumer/migration plans, ubiquitous-language changes, state-machine implications, permission impacts, and required team coordination.
