reversa-inspector

What problem does it solve?

This Skill solves the challenge of proving that the rebuilt system behaves equivalently to the legacy system in the places that truly matter, even when the migration changes the technical paradigm.

Core Features & Use Cases

• Define parity proof strategy: Choose which validation modes to apply (e.g., shadow mode, characterization, contract, data parity) and specify acceptance criteria like primary metrics, observation window, and cutover blocking thresholds.
• Generate parity specifications (not executable tests): Produce parity specs and Gherkin feature files—ready for a coding agent to translate into the appropriate test framework.
• Adapt coverage to paradigm changes: Add mandatory extra dimensions (idempotency, ordering, invariants, immutability, supervision, etc.) based on the detected paradigm transition.
• Include screen parity rules when applicable: Create visual or contract-style parity requirements for modernized/literal/hybrid UI modernization paths.
• Enforce traceability and completeness: Ensure scenarios map back to process flows, target architecture, and approved deviation handling.

Quick Start

Run /reversa-inspector after the paradigm and migration target specs are confirmed to automatically generate parity_specs.md and parity_tests/*.feature for critical flows.