What problem does it solve? Before committing to architecture, AL/Business Central features need a settled user-facing journey — who acts, what happens, and what the user sees — expressed in BC vocabulary rather than AL implementation terms. This Skill produces that artifact as event-model.md, preventing fuzzy Role names, fictitious Business Events, and re-litigated user-side decisions during design. ## Core Features & Use Cases - Event Modeling for BC: Settles Role, Action, Business Event, View, and Status slots on a single timeline with Role swimlanes, following Event Modeling lineage. - BaseApp grounding: Routes Role Center names, BaseApp Business Events, and Status enums through /al-research so canonical names are verified instead of invented. - Branch and spec-folder setup: Creates the feature branch and specs/<NNN>-<slug>/ folder when run first on main, then writes a telegraphic event-model.md. - Use Case: After running /al-grill-adr on a credit-limit override feature, run this Skill to settle the journey — Order Processor releases an order, Credit Limit Breached fires, the override cue increments — before /al-design commits architecture. ## Quick Start Run /al-event-model after /al-grill-adr to settle the user-facing journey for my feature into event-model.md.
