domain-model

To map plugin boundaries from event storm results, this Skill analyzes clustered events, actors, and rules to identify business domains. It produces a domain map that guides plugin ownership and defines the exact scope for each plugin in your architecture planning.

The best way to decide how many plugins to build is to evaluate domain clusters against status data and event storm outputs. This identifies clear domain boundaries and outputs a candidate plugin map defining exactly what each plugin owns.

Grouping business events into domain clusters requires evaluating event storm outputs against shared data, actors, and business rules. This analysis identifies natural domain boundaries and generates a domain map with candidate plugins for your architecture.

Yes, you need completed event storm outputs before mapping domain boundaries. This Skill reads workspace artifacts containing your events and processes to evaluate domain clusters and generate the final domain map with candidate plugins.

You should not use domain clustering for plugin architecture if you lack completed event storm outputs or workspace artifacts with status data. Without these prerequisites, the tool cannot evaluate domains or produce a candidate plugin map.