What problem does it solve? When migrating a legacy system to a new architecture or paradigm, teams struggle to prove the new system behaves equivalently to the old one. This Skill defines the validation strategy and produces parity specifications adapted to the chosen paradigm transition. ## Core Features & Use Cases - Parity Strategy Definition: Selects validation modes (shadow mode, characterization tests, contract tests, data parity) and defines acceptance criteria such as divergence thresholds and observation windows. - Paradigm-Adapted Coverage: Adjusts required test dimensions based on the paradigm transition (e.g., synchronous to event-driven requires idempotency, ordering, and queue-failure scenarios). - Gherkin Spec Generation: Produces one .feature file per critical flow with traceability to process flows, target architecture, and business rules, including screen parity scenarios when a UI exists. - Use Case: After migrating a monolithic OO system to an event-driven architecture, invoke this Skill to generate parity specs requiring idempotency and message-ordering scenarios for every critical flow before cutover. ## Quick Start Run /reversa-inspector after the migration strategy and target architecture are approved to generate parity_specs.md and Gherkin parity tests for all critical flows.
