reversa-paradigm-advisor

Detects legacy system paradigms and guides migration paradigm decisions from spec artifacts.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/RLuf/fzagent --skill reversa-paradigm-advisor-rluf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-paradigm-advisor-rluf

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 syntax change end up with broken mental models. This Skill detects the legacy paradigm from specification artifacts, infers the natural paradigm of the target stack, and forces a conscious, documented decision before any code is written. ## Core Features & Use Cases - Paradigm Detection: Classifies the legacy system (procedural, OO classic, OO with DI, functional, event-driven, actor model, dataflow, hybrid) using evidence from _reversa_sdd/ artifacts with confidence tagging (CONFIRMED, INFERRED, GAP, AMBIGUOUS). - Gap Analysis: Maps the legacy-to-target paradigm pair against a catalog of typical gaps and presents at least four concrete implications citing real rules and flows from the legacy system. - Decision Recording: Presents three options (adopt natural paradigm, force legacy paradigm, hybrid), collects the user's choice, and writes paradigm_decision.md with a derived appetite (conservative, balanced, transformational) for downstream agents. - Use Case: A team migrating a Rails monolith to Node.js runs this Skill first; it detects OO classic with Active Record, infers event-driven as Node's natural paradigm, and documents the user's choice so the Curator, Strategist, Designer, and Inspector agents honor it. ## Quick Start Run /reversa-paradigm-advisor after the migration brief exists to analyze the legacy paradigm and record the paradigm decision for the migration team.

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 Skill reads `_reversa_sdd/` documents and tags each classification with a confidence level from confirmed to ambiguous.

What is a paradigm gap when migrating between stacks?▼

A paradigm gap is the mismatch between the legacy system's paradigm and the target stack's natural paradigm, such as moving from synchronous OO to event-driven Node.js. It implies concrete changes like error handling becoming retry/DLQ patterns and responses becoming asynchronous.

What inputs does the reversa-paradigm-advisor skill require?▼

It requires `_reversa_sdd/migration/migration_brief.md` with a declared target stack, plus discovery artifacts like domain.md, architecture.md, and inventory.md. If prerequisites are missing, it stops and directs the user to run /reversa-migrate or /reversa first.

Does this skill analyze legacy source code directly?▼

No, it operates entirely at the specification level and never reads legacy source code. All paradigm detection is inferred from artifacts produced by the discovery team in the `_reversa_sdd/` directory.

What happens when the legacy paradigm cannot be determined?▼

The skill records the paradigm as a GAP (LACUNA) with red confidence tagging and asks the user to confirm based on their own knowledge of the legacy system. It never invents evidence without a reference to a source artifact.