reversa-inspector

Define paradigm-aware parity criteria and generate Gherkin parity test specifications for system migrations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The reversa-inspector skill solves the risk of breaking user-critical behavior during migration by defining rigorous, paradigm-aware acceptance criteria that compare the new system to the legacy.

Core Features & Use Cases

  • Parity strategy definition: selects validation modes (e.g., shadow, characterization, contract, data parity) and sets explicit acceptance metrics, observation windows, and cutover blocking rules.
  • Paradigm-adapted coverage: enforces additional parity dimensions when the migration changes paradigms (e.g., event ordering, idempotency, eventual consistency, invariants, immutability, supervision).
  • Flow-critical parity specs: produces parity artifacts as specs (not executable tests), generating parity_tests/*.feature in valid Gherkin format with consistent tags and traceability.

Quick Start

Ask an AI agent workflow to run the reversa-inspector on the confirmed migration SDD inputs to generate _reversa_sdd/migration/parity_specs.md and parity_tests/*.feature with the appropriate parity coverage for the target paradigm.

Frequently Asked Questions about reversa-inspector

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

FAQPage Schema
How do I prove migration parity between a legacy system and a new system?

Migration parity is proven by defining paradigm-aware acceptance criteria that compare behavioral equivalence, producing parity specs and Gherkin feature files for critical flows during migration handoff.

What validation modes can I use for migration parity testing?

Migration parity testing supports shadow, characterization, contract, and data parity validation modes, each with explicit acceptance metrics, observation windows, and cutover blocking rules to ensure behavioral equivalence.

How do I generate Gherkin specs for critical migration flows?

Gherkin parity specs are generated by adapting parity criteria to the confirmed target paradigm, producing valid .feature files with consistent tags and traceability for critical flow coverage during migration handoff.

When do I need idempotency and eventual consistency checks in migration parity specs?

Idempotency and eventual consistency checks are required in parity specs when the migration changes paradigms, enforcing additional parity dimensions like event ordering, invariants, immutability, and supervision for the target system.

Do I need screen parity rules for UI modernization migrations?

Screen parity rules are required when a UI is present and the modernization mode requires it, extending the parity specs to validate that the migrated interface preserves critical legacy behavior.

What inputs are required to generate parity specs for a system migration?

Generating parity specs requires confirmed inputs from paradigm, strategy, architecture, screen decisions, and characterization or code analysis artifacts to produce parity_specs.md and Gherkin .feature files in the migration directory.