reversa-paradigm-advisor

Detect legacy programming paradigms and infer target stack paradigms for migration planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents teams from treating a migration as a superficial syntax change by detecting the legacy system’s programming paradigm, inferring the target stack’s natural paradigm, and forcing an explicit decision with concrete trade-offs.

Core Features & Use Cases

  • Legacy paradigm detection from specs: Classifies the legacy paradigm using evidence from _reversa_sdd/ artifacts (without reading legacy source code).
  • Target stack natural paradigm inference: Maps the declared target stack in migration_brief.md to the most natural paradigm and outlines viable alternatives.
  • Gap analysis with concrete implications: Produces paradigm_decision.md using the paradigm catalog’s gap table plus at least four concrete implications tied to specific legacy components/flows.
  • Decision capture for downstream agents: Writes a structured decision artifact that all later agents must read first.

Quick Start

Ask /reversa-paradigm-advisor after running /reversa-migrate to ensure _reversa_sdd/migration/migration_brief.md exists and _reversa_sdd/ is populated.

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 for migration planning?

You detect the legacy programming paradigm by classifying evidence extracted from specification artifacts stored in the `_reversa_sdd/` directory, analyzing structured documentation rather than requiring direct access to legacy source code.

How do I analyze paradigm gaps between a legacy system and a target stack?

Analyze paradigm gaps by mapping the declared target stack to its natural paradigm, then highlighting structural mismatches with concrete, evidence-cited implications tied to specific legacy components and flows.

What is the best way to document architecture decisions for a legacy modernization migration?

Document architecture decisions by generating a structured `paradigm_decision.md` file that captures explicit paradigm choices, trade-offs, and evidence traceability for downstream agent workflows to consume before implementation proceeds.

Do I need specification artifacts to plan a legacy modernization paradigm migration?

Yes, specification artifacts are required; migration planning enforces prerequisite checks for `_reversa_sdd/` population and a declared target stack in `migration_brief.md` before producing any paradigm decision output.

Why does migration planning fail when treating legacy modernization as a syntax change?

Migration planning fails because superficial syntax changes ignore fundamental paradigm gaps between the legacy system and target stack, causing structural mismatches that require explicit, evidence-based architecture decisions before implementation.