reversa-paradigm-advisor

Detects legacy programming paradigms from specs and guides migration paradigm decisions.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-paradigm-advisor-ruggery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/Ruggery/OCR_Cartorio/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-paradigm-advisor-ruggery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a legacy system to a new stack often hides a deeper shift in programming paradigm (procedural, OO, functional, event-driven), and teams that treat it as a mere syntax change end up with broken mental models and costly rework. ## Core Features & Use Cases - Paradigm Detection: Classifies the legacy system's paradigm from _reversa_sdd/ specification artifacts with confidence-tagged evidence (confirmed, inferred, gap, ambiguous). - Stack Mapping: Infers the natural paradigm of the declared target stack using a built-in catalog covering Node.js, Go, Rust, Elixir, Python, .NET, Java, Ruby, and more. - Guided Decision: Presents three concrete options (adopt target paradigm, force legacy paradigm, or hybrid) with at least four system-specific implications, then records the user's choice and derived appetite in paradigm_decision.md. - Use Case: When migrating a classic Rails monolith to an event-driven Node.js backend, run this agent first to surface how synchronous flows become asynchronous with retries and DLQs before any code is written. ## Quick Start Ask the agent to analyze the legacy specs in _reversa_sdd and produce a paradigm decision for the target stack declared in the migration brief.

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 migration?▼

Analyze the system's specification artifacts for signals like aggregates, inheritance, event flows, or linear controller logic, then classify against a paradigm catalog. This agent reads _reversa_sdd documents and tags each finding with a confidence level from confirmed to ambiguous.

What is a paradigm gap in legacy system migration?▼

A paradigm gap is the difference between the legacy system's programming model and the natural paradigm of the target stack, such as moving from synchronous procedural code to event-driven architecture. It implies concrete changes like retries, DLQs, and idempotency rather than just syntax translation.

Which paradigm fits a Node.js or Go migration target?▼

Node.js naturally fits event-driven asynchronous design, with OO plus DI as a viable alternative via NestJS. Go favors CSP-style concurrency with goroutines and channels, simulating OO through interfaces. The catalog maps ten common stacks to their natural paradigms.

What inputs does the paradigm advisor need to run?▼

It requires a migration_brief.md with the declared target stack and populated _reversa_sdd discovery artifacts such as domain.md, architecture.md, and inventory.md. It operates only on specifications and never reads legacy source code.

What happens if the legacy paradigm cannot be determined from specs?▼

The agent records the paradigm as a gap (LACUNA) and asks the user to confirm based on their knowledge of the legacy system. It never invents evidence without a reference to a source artifact.