skills.rest
stribus
stribusCOMMUNITY
Explore all skills by this author →
GitHub

reversa-inspector

Generate parity specifications and Gherkin feature files for system migrations.

1|Updated Nov 20, 2025
Search Tags:#specification#migration#gherkin#parity#parity-specs#parity-tests
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-inspector-stribus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-inspector-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prove behavioral parity between the legacy system and the new system during migration by generating parity artifacts (parity_specs.md and parity_tests/*.feature) to guide validation.

Core Features & Use Cases

  • Generates parity_specs.md describing the validation strategy and required parity criteria.
  • Produces parity_tests/*.feature files for critical flows as Gherkin artifacts (not executable tests).
  • Integrates with pre-migration artifacts and paradigm decisions to ensure traceability.

Quick Start

Run the inspector to generate parity_specs.md and parity_tests/*.feature for critical migration 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 new system during migration?▼

Migration parity is verified by generating parity specifications and Gherkin feature files for critical flows. These artifacts describe the validation strategy and required criteria to prove the new system matches legacy behavior.

What are Gherkin feature files used for in migration validation?▼

Gherkin feature files serve as parity artifacts during migration to document and validate critical flows. They are generated as specification artifacts rather than executable tests, ensuring behavioral traceability between systems.

How do I generate parity specifications for critical migration flows?▼

Generate parity specifications by running the inspector on critical migration flows. It reads prerequisite decision artifacts and outputs parity_specs.md detailing the validation strategy alongside Gherkin feature files.

Do I need prerequisite decision artifacts before generating parity tests?▼

Yes, prerequisite decision artifacts like pre-migration and paradigm decisions are required. The inspector reads these to generate accurate parity specifications and Gherkin feature files with full traceability.

Are the generated Gherkin feature files executable tests?▼

No, the generated Gherkin feature files are not executable tests. They serve as parity artifacts to guide validation and document behavioral expectations between legacy and new systems during migration.

Related Skills

Explore More Software Engineering Skills→
ricardops34ricardops34

reversa-inspector

Generate parity specifications and Gherkin feature files for migrated systems.

Community
Advanced
cliffthelincliffthelin

reversa-inspector

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

Community
Advanced
sandecosandeco
1.5k

reversa-inspector

Generates migration parity specs and Gherkin test scenarios for legacy-to-target systems.

Community
Advanced
sddevelopment-besddevelopment-be
13

Test Readability and Clarity Check Approach

Analyzes code tests to reconstruct system behavior understanding and generate living specification artifacts.

Official
Intermediate