state-machine-transition

Add new states by extending the State enum with well-scoped, documented state definitions. Define corresponding entries in VALID_TRANSITIONS to specify allowed transitions from each new state, and implement _enter_<state>() and _exit_<state>() methods to handle entry and exit actions when the FSM transitions into or out of that state.

Define valid transitions explicitly in a VALID_TRANSITIONS structure that maps each state to its allowed destination states. This pattern preserves system stability by preventing invalid state changes and serves as the single source of truth for your FSM's control flow and event-driven behavior.

Implement _enter_<state>() methods to execute logic when entering a state and optional _exit_<state>() methods for cleanup or side-effects when leaving. Register event handlers to trigger transitions and publish StateChangedEvent to notify observers of state changes and associated entry/exit action outcomes.

Yes. Define state timeouts in a STATE_TIMEOUTS structure and implement _on_timeout() method to handle timeout-driven transitions. This allows states to automatically transition after a specified duration, enabling time-based state machine behavior alongside event-driven transitions.

Unit test new transitions by verifying state changes, validating entry/exit action execution, confirming StateChangedEvent publication, and checking timeout behavior. The Skill includes a pattern for comprehensive transition testing to ensure stability when extending the FSM.

Yes. Register event handlers explicitly to trigger transitions—for example, on_your_trigger_event methods that call the state transition logic. This explicit wiring ensures clarity about which events drive which state changes and maintains full control over your FSM's event-driven behavior.