reversa-inspector

Migration parity is proven by defining adaptable parity criteria and generating validation artifacts. This Skill produces parity_specs.md and executable Gherkin feature files to capture behavioral equivalence and guide your validation process.

The best way to generate Gherkin feature files for migration parity testing is by running the parity workflow, which outputs executable parity_tests/*.feature files. These files capture critical flows to validate behavioral equivalence between systems.

To document equivalence specs for a system migration project, you generate a parity_specs.md file. This Skill automatically creates this document in the _reversa_sdd/migration/ directory to ensure traceability and handoff.

Yes, you can use parity specifications and feature files for critical migration flows. The workflow applies parity assessment specifically to critical flows, producing artifacts that capture and validate behavioral equivalence.

Migration parity artifacts are stored in the _reversa_sdd/migration/ directory. This ensures that your parity_specs.md and parity_tests/*.feature files remain organized for traceability and handoff.

No, you do not need optional scripts and references to validate behavioral equivalence. The core workflow generates required parity artifacts, while scripts, references, and assets are loaded optionally as needed.