skills.rest
lacsousa
lacsousaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-paradigm-advisor

Detects legacy programming paradigms and guides migration decisions for target stacks.

Updated Jun 12, 2026
Search Tags:#decision record#software architecture#event-driven#code modernization#stack analysis#legacy migration#paradigm detection
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-paradigm-advisor-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-paradigm-advisor-lacsousa

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 paradigm shift (e.g., procedural to event-driven) that teams mistake for a simple syntax change. This Skill detects the legacy paradigm from specification artifacts, infers the natural paradigm of the target stack, and forces a conscious, documented decision before migration proceeds. ## Core Features & Use Cases - Paradigm Detection: Classifies the legacy system as procedural, OO classic, OO with DI, functional, event-driven, actor model, dataflow, or hybrid, with citable evidence and confidence levels (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 drawn from the actual legacy system. - Decision Recording: Presents three options (adopt natural paradigm, force legacy paradigm, hybrid), captures the user's choice and justification, and writes a paradigm_decision.md artifact consumed by downstream migration agents. - Use Case: A team migrating a Rails monolith to Node.js runs this agent first; it detects OO classic with Active Record, infers event-driven as Node's natural paradigm, and documents the user's chosen strategy for the Curator, Strategist, Designer, and Inspector agents. ## Quick Start Run /reversa-paradigm-advisor after the migration brief exists to analyze the legacy paradigm and record a paradigm decision for the target stack.

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 specification artifacts such as domain models, architecture documents, and process flows for signals like aggregates, inheritance, events, or immutable types. This Skill classifies the result as procedural, OO, functional, event-driven, actor model, dataflow, or hybrid with evidence citations.

What is the natural paradigm of a target stack like Node.js or Go?▼

Each stack has a natural paradigm: Node.js is event-driven asynchronous, Go favors CSP-style concurrency, Elixir uses the actor model, and Spring or .NET favor OO with dependency injection. The Skill infers this from a stack-to-paradigm mapping table in its reference catalog.

What inputs does the paradigm advisor need to run?▼

It requires a migration_brief.md with the declared target stack and populated discovery artifacts such as domain.md, architecture.md, and inventory.md in the _reversa_sdd directory. It never reads legacy source code directly.

What happens when the legacy and target paradigms differ?▼

The Skill presents at least four concrete implications using examples from the legacy system, then offers three options: adopt the target's natural paradigm, force the legacy paradigm, or use a hybrid. The user's choice and justification are recorded in paradigm_decision.md.

Can the paradigm advisor run without an interactive chat?▼

Yes. In non-interactive engines it writes a pending_decisions.md file containing the three options into the migration folder and waits for a human to record the decision before downstream agents proceed.

Related Skills

Explore More Software Engineering Skills→
ggazzoggazzo

reversa-curator

Analyze legacy specifications and migration briefs to generate target business rules and discard logs.

Community
Advanced
Pabloprogramador23Pabloprogramador23

reversa-paradigm-advisor

Detect legacy paradigms from specs and guide migration decisions.

Community
Advanced
afsjrafsjr

reversa-paradigm-advisor

Detect legacy programming paradigms from migration specs and write paradigm_decision.md.

Community
Advanced
EmeaAppGbbEmeaAppGbb

rewrite-planner

Plan component-by-component rewrites using the Strangler Fig pattern.

Official
Advanced