reversa-paradigm-advisor

Detect legacy and target programming paradigms from Reversa SDD specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents migration teams from treating a legacy-to-target change as mere syntax by detecting the legacy programming paradigm and forcing an explicit decision about how to handle paradigm gaps.

Core Features & Use Cases

  • Paradigm detection from specs: Classifies the legacy paradigm using only _reversa_sdd/ artifacts (no legacy source code).
  • Target paradigm inference: Infers the natural paradigm of the target stack from migration_brief.md using the local paradigm catalog.
  • Gap concretization + decision forcing: Presents concrete, example-driven implications and always offers three options, recording the user's choice into paradigm_decision.md.

Quick Start

Run /reversa-paradigm-advisor to generate _reversa_sdd/migration/paradigm_decision.md after confirming that the required _reversa_sdd/ brief artifacts exist.

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 the programming paradigm of a legacy system before migrating it?

Paradigm detection classifies the legacy programming paradigm using only `_reversa_sdd/` specification artifacts, without requiring access to legacy source code. This allows migration teams to identify structural patterns early and plan architectural shifts accurately.

How do I handle paradigm mismatch risks when planning a NestJS migration?

To handle paradigm mismatch risks, the advisor infers the natural paradigm of the target stack from `migration_brief.md` and concretizes the gap implications. It forces an explicit decision by presenting concrete examples and recording the chosen resolution approach.

Do I need legacy source code to run paradigm detection for software migration?

No legacy source code is required for paradigm detection. The analysis operates exclusively on `_reversa_sdd/` specification artifacts, classifying the legacy paradigm and inferring the target stack's natural paradigm to highlight architectural gaps.

What is the best way to document architectural decisions for paradigm gaps during migration?

The best way to document paradigm gap decisions is by generating a populated `_reversa_sdd/migration/paradigm_decision.md` file. This enforces prerequisite checks, uses a local paradigm catalog, and records the user's explicit choice among three provided options.

Why must I choose between three options when resolving a paradigm mismatch?

Choosing between three options forces an explicit decision about handling paradigm gaps, preventing teams from treating legacy-to-target changes as mere syntax conversions. This workflow concretizes downstream implications and records the resolution into `paradigm_decision.md`.