What problem does it solve? When migrating a legacy system to a new architecture or paradigm, teams need a rigorous way 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 parity_specs.md and one .feature file per critical flow with full traceability to process flows, target architecture, and business rules. - Use Case: After a migration team decides to move a procedural legacy system to an event-driven architecture, invoke this Skill to generate parity specs covering message ordering, idempotency, and DLQ behavior for every critical flow. ## Quick Start Run /reversa-inspector after the migration strategy and target architecture are approved to generate parity_specs.md and Gherkin parity test files in _reversa_sdd/migration/.
