reversa-paradigm-advisor

Detect paradigm mismatches and generate a decision document for system migration.

Updated May 11, 2026

Search Tags:#technical debt #decision support #code migration #system migration #paradigm analysis

Ready to run

npx skills add https://github.com/Marcu-Loreto/Skill_v1 --skill reversa-paradigm-advisor-marcu-loreto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/Marcu-Loreto/Skill_v1/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/Marcu-Loreto/Skill_v1 --skill reversa-paradigm-advisor-marcu-loreto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies and advises on paradigm mismatches during system migration, ensuring informed decisions and reducing technical debt.

Core Features & Use Cases

Paradigm Detection: Identifies the programming paradigm of the legacy system and infers the natural paradigm of the target stack.
Gap Analysis: Alerts about paradigm gaps and guides users in making conscious decisions.
Decision Documentation: Produces a comprehensive paradigm decision document for future reference.
Use Case: For a company migrating from a procedural legacy system to an event-driven target stack, this Skill helps assess the implications and make a well-informed decision.

Quick Start

Run the 'reversa-paradigm-advisor' command to initiate the paradigm analysis.

Frequently Asked Questions about reversa-paradigm-advisor

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

FAQPage Schema

How do I detect paradigm mismatches during a system migration?▼

A paradigm mismatch occurs when the legacy system's programming paradigm conflicts with the target stack's natural paradigm. This Skill analyzes system documentation and migration briefs to identify these gaps and advise on reducing technical debt.

How do I analyze technical debt risks when migrating to an event-driven architecture?▼

Analyze technical debt risks by running a paradigm analysis against your system documentation and migration brief. The Skill produces a decision document detailing paradigm gaps, evidence, and implications for the target stack transition.

What do I need to provide to assess procedural to event-driven paradigm gaps?▼

You need to provide system documentation and a migration brief to assess paradigm gaps. The Skill uses these inputs to detect the legacy programming paradigm and infer the target stack's paradigm for a comprehensive gap analysis.

Can I generate a paradigm decision document for a code migration project?▼

Yes, you can generate a paradigm decision document by running the paradigm analysis. It outputs comprehensive reference documentation containing evidence and implications of paradigm mismatches identified during the system migration.

When should I perform a paradigm analysis before starting a system migration?▼

Perform a paradigm analysis before starting a system migration to ensure informed decisions and reduce technical debt. It is essential when moving between distinct paradigms, such as from a procedural legacy system to an event-driven target stack.