What problem does it solve? Business rules are often described inconsistently, and critical facts like exceptions, time-based triggers, and cancellations never surface in interviews. This Skill systematically enumerates what actually happens in a business domain as discrete, past-tense business events before any design or documentation work begins. ## Core Features & Use Cases - Chronological Event Enumeration: Lists business events in the order they occur, each with trigger (operation, time, external, or chained), actor, preconditions, business outcome, confidence level, and source. - Granularity Discipline: Applies explicit criteria for what counts as one event, separating facts that can be cancelled independently or have different triggers, and translating system-level actions (button clicks, saves, batches) into underlying business facts. - Confidence Tracking: Marks each event as confirmed, assumed, or unknown so unverified hypotheses never mix with established facts, and reports what remains unconfirmed and who can verify it. - Use Case: When asked to map out how a reservation cancellation process works, this Skill walks the main flow first, then branches into exceptions, time-based triggers, external events, and cleanup actions, producing a sourced event list without jumping to design. ## Quick Start Ask the agent to enumerate the business events that occur in the reservation cancellation process, listing each event with its trigger, actor, and confidence level.
