reversa-paradigm-advisor

Detect legacy and target programming paradigms from _reversa_sdd/ specs and write paradigm_decision.md.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-paradigm-advisor-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-paradigm-advisor-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents silent, high-risk paradigm mismatches during migration by diagnosing the legacy programming paradigm, inferring the natural paradigm of the target stack, and forcing a conscious decision about how to bridge the gap.

Core Features & Use Cases

  • Legacy paradigm detection from specs: Classifies the legacy paradigm using only _reversa_sdd/ artifacts (no source-code inspection), with citably tagged confidence levels (🟢/🟡/🔴/⚠️).
  • Target paradigm inference: Uses the local paradigm catalog to map the declared target stack (from migration_brief.md) to its natural paradigm and viable alternatives.
  • Gap concretization + decision artifact: Produces _reversa_sdd/migration/paradigm_decision.md using the provided template, including concrete implications and pending actions for subsequent migration agents.

Quick Start

Run the migration briefing first so the skill can read _reversa_sdd/migration/migration_brief.md, then activate /reversa-paradigm-advisor to generate paradigm_decision.md in _reversa_sdd/migration/.

Frequently Asked Questions about reversa-paradigm-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine the programming paradigm of a legacy system from specifications without source code?

You can determine the legacy programming paradigm by analyzing specification artifacts within the `_reversa_sdd/` directory, classifying the paradigm with citable confidence levels rather than inspecting source code directly.

How do I avoid programming paradigm mismatches during migration planning?

To avoid paradigm mismatches during migration planning, diagnose the legacy paradigm, infer the target stack's natural paradigm, and produce a deterministic paradigm_decision.md artifact to bridge the gap consciously.

Can I infer the target stack paradigm using a local paradigm catalog?

Yes, target paradigm inference maps the declared target stack from the migration_brief.md to its natural paradigm and viable alternatives by consulting the local paradigm catalog.

What is needed to generate a paradigm_decision.md artifact for downstream agents?

Generating a paradigm_decision.md artifact requires reading the migration_brief and relevant architecture, inventory, or code-analysis specs, consulting the local paradigm catalog, and populating the provided template.

Does paradigm migration analysis work without source-code inspection?

Yes, legacy paradigm detection works exclusively by reading `_reversa_sdd/` specification artifacts, bypassing source-code inspection entirely to produce an evidence-based paradigm decision.