What problem does it solve? When migrating a legacy system to a new architecture, teams need a rigorous way to prove the new system behaves equivalently to the old one. This Skill defines parity validation strategies adapted to the target paradigm and produces traceable Gherkin specifications for critical flows. ## 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 completing a migration design from a procedural legacy system to an event-driven architecture, invoke this Skill to generate parity_specs.md and Gherkin scenarios covering parity, idempotency, and message ordering for each critical flow. ## Quick Start Run /reversa-inspector after the migration strategy and target architecture are approved to generate parity specs and Gherkin feature files for all critical flows.
