reversa-inspector

Generate parity specifications and Gherkin feature files for migrated systems.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about reversa-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prove behavioral parity between a legacy system and a migrated system?

Behavioral parity during migration is proven by defining validation modes like shadow mode or contract testing, setting cutover thresholds, and generating Gherkin-ready parity specifications mapping critical flows to target architecture.

What is paradigm-aware parity testing in system migrations?

Paradigm-aware parity testing adapts coverage dimensions to technical transitions by adding mandatory checks for idempotency, ordering, invariants, immutability, and supervision based on the detected paradigm shift between legacy and target systems.

How do I write Gherkin feature files for migration equivalence testing?

Generate Gherkin feature files for migration equivalence by mapping critical process flows to target architecture, defining accepted parity thresholds, and optionally including screen parity validation rules for UI modernization paths.

Can I use parity specifications to validate screen parity during UI modernization?

Yes, parity specifications can include visual or contract-style screen parity validation rules tailored for modernized, literal, or hybrid UI modernization paths to ensure interface equivalence during migration.

What is the best way to define a parity proof strategy for a system migration?

The best way to define a parity proof strategy is to select validation modes like data parity or characterization, specify primary metrics and observation windows, and establish cutover blocking thresholds before generating parity specs.

Do I need executable tests to verify migration behavioral equivalence?

No, you do not need executable tests initially; you can generate Gherkin-ready parity specifications and a parity_specs.md file, which a coding agent then translates into the appropriate executable test framework.