What problem does it solve? Testing stateful systems like payment flows, authentication, and order workflows often misses transitions, guard conditions, and error paths because test cases are written ad hoc. This Skill builds a formal state machine model from acceptance criteria first, then derives test cases systematically so coverage is measurable and auditable. ## Core Features & Use Cases - State Machine Modeling: Build ASCII or UML state diagrams with explicit states, transitions, guards, and actions before writing any test case. - Coverage-Driven Test Generation: Derive test cases targeting node coverage (95%), edge coverage (85%), and risk-driven path coverage, including guard-true, guard-false, and error-recovery paths. - State Explosion Mitigation: Apply aggregation, transient-state elimination, orthogonal FSM separation, and hierarchical decomposition to keep complex models testable. - Use Case: Given an acceptance criterion like "user logs in with email, password, and OTP", produce a full authentication FSM with 18 derived test cases covering lockout, OTP expiry, retries, and notification side-effects. ## Quick Start Ask the AI to design a state machine model and derive coverage-based test cases for your payment or authentication workflow acceptance criteria.