skills.rest
Rdinda
RdindaCOMMUNITY
Explore all skills by this author →
GitHub

reversa-inspector

Generate parity specs and Gherkin scenario files for migration validation.

1|Updated Dec 20, 2025
Search Tags:#migration#spec generation#gherkin#UI validation#behavioral parity#paradigm adaptation#resilience criteria
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-inspector-rdinda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-inspector-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps migration teams prove that the new system is behaviorally equivalent to the legacy one in the critical places where it matters, especially when the paradigm changes.

Core Features & Use Cases

  • Produces parity specifications that translate equivalence goals into clear acceptance criteria (metrics, windows, and cutover blockers).
  • Generates parity scenarios in Gherkin (specs, not executable tests) for each critical flow and—when applicable—for UI parity validation.
  • Adapts parity coverage to paradigm transitions, adding required dimensions like idempotency, message order, DLQ behavior, supervision, or aggregate invariants.

Quick Start

Use the reversa-inspector skill to read the confirmed migration decisions and legacy flow analysis, then generate parity_specs.md and parity_tests/*.feature for the selected validation modes.

Frequently Asked Questions about reversa-inspector

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

FAQPage Schema
How do I validate behavioral equivalence when migrating a system to a new paradigm?▼

Behavioral parity validation requires generating parity specifications and Gherkin scenario files that define acceptance metrics, cutover blockers, and per-flow traceability for the target paradigm. This confirms the migrated system matches legacy behavior.

What are Gherkin parity scenarios and when do I need them for migration handoff?▼

Gherkin parity scenarios are spec files defining expected equivalence for each critical flow during migration handoff. You need them when transitioning paradigms to establish traceable acceptance criteria and validate behavioral confidence.

How do I generate parity specs for UI validation and critical flow transitions?▼

Generate parity specs by selecting validation modes, setting acceptance metrics and cutover blockers, then producing per-flow Gherkin scenarios. Include optional screen or characterization inputs to cover UI parity validation during migration.

Does migration parity validation adapt coverage for paradigm transitions like event-driven architectures?▼

Yes, parity validation adapts coverage for paradigm transitions by adding required dimensions like idempotency, message order, DLQ behavior, supervision, or aggregate invariants. This ensures behavioral equivalence across architectural shifts.

What's the best way to define cutover blockers and acceptance metrics for a legacy system migration?▼

Define cutover blockers and acceptance metrics by producing a parity specification that translates equivalence goals into clear criteria, coupled with Gherkin scenarios mapping per-flow traceability for critical legacy paths during migration.

What limitations exist when using Gherkin scenarios for migration parity validation?▼

Gherkin scenarios for migration parity validation are specifications, not executable tests. They require manual implementation to execute, and coverage depends on selected validation modes and available characterization inputs for the target paradigm.

Related Skills

Explore More Software Engineering Skills→
AlexandrePontesjrAlexandrePontesjr

reversa-inspector

Generate parity specs and Gherkin parity scenarios for legacy-to-target migrations.

Community
Advanced
CyanAutomationCyanAutomation
1

ci-quality-gates

Reproduce CI quality gates locally to diagnose PR failures.

Community
Intermediate
afsjrafsjr

reversa-inspector

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

Community
Advanced
cliffthelincliffthelin

reversa-inspector

Generate paradigm-adapted parity specifications and Gherkin scenarios for Reversa migrations.

Community
Advanced