reversa-paradigm-advisor

Classifies legacy and target-stack paradigms from Reversa specifications and writes a migration decision file.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-paradigm-advisor-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-paradigm-advisor
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-paradigm-advisor-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents AI-assisted legacy migrations from treating a paradigm shift as a mere syntax change by first detecting the legacy programming paradigm and comparing it to the natural paradigm of the target stack.

Core Features & Use Cases

  • Legacy paradigm detection from specs: Classifies the legacy paradigm using only _reversa_sdd/ artifacts (domain, architecture, inventory, and optional flow analysis) with evidence tagging.
  • Target-stack natural paradigm inference: Infers the natural paradigm from migration_brief.md via a local paradigm catalog and proposes viable alternatives.
  • Gap clarification with actionable implications: Quantifies the migration impact by presenting concrete implications and mandatory options for the user, then writes _reversa_sdd/migration/paradigm_decision.md as required input for subsequent agents.

Quick Start

Run the migration orchestrator that invokes this agent (e.g., ask for /reversa-migrate) after ensuring _reversa_sdd/migration/migration_brief.md and the discovery specs are present.

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 legacy programming paradigm gaps before an AI migration?

Detect legacy paradigm gaps by classifying the source system from specifications and comparing it to the target stack's natural paradigm. This prevents AI migrations from incorrectly treating structural shifts as simple syntax changes.

What happens when a legacy modernization paradigm shift breaks correctness?

When a paradigm shift threatens correctness during legacy modernization, the system quantifies the impact and presents mandatory options for user decision capture. This ensures the migration handles structural paradigm gaps properly.

How to infer the natural programming paradigm of a target stack from a migration brief?

Infer the target stack's natural programming paradigm by analyzing the migration_brief.md against a local paradigm catalog. This process proposes viable alternative paradigms to ensure the target architecture aligns with the code.

Do I need Reversa specifications to classify a legacy system's paradigm?

Yes, you need Reversa specifications to classify a legacy system's paradigm using domain, architecture, and inventory artifacts. The classification relies on these artifacts with evidence tagging to accurately determine the programming approach.

Can I use spec reverse engineering for migration planning without automated flow analysis?

Spec reverse engineering can classify the legacy paradigm using domain, architecture, and inventory artifacts without flow analysis. However, including optional flow analysis provides additional evidence tagging for more accurate migration planning.

Why does treating a paradigm shift as a syntax change break migration correctness?

Treating a paradigm shift as a syntax change breaks migration correctness because it ignores fundamental structural differences between the legacy and target systems. Detecting these gaps early ensures the architecture matches the target stack's natural paradigm.