reversa-paradigm-advisor

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-paradigm-advisor-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-paradigm-advisor-tjsasakifln

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. This Skill detects the legacy paradigm from specification artifacts, infers the natural paradigm of the target stack, and forces a conscious, documented human decision on how to handle the gap. ## 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) drawn from _reversa_sdd/ artifacts. - Stack-to-Paradigm Mapping: Infers the natural paradigm of the declared target stack (Node.js, Go, Rust, Elixir, Python, Kotlin, .NET, Java, Ruby, serverless TypeScript) using a bundled reference catalog. - Guided Decision Workflow: Presents concrete gap implications with legacy examples, offers three options (adopt natural paradigm, force legacy paradigm, hybrid), and records the user's choice plus derived appetite in paradigm_decision.md. - Use Case: During a COBOL-to-Node.js migration, run this Skill first so the team explicitly decides how synchronous batch flows become asynchronous event-driven handlers before any code is written. ## Quick Start Ask the agent to run /reversa-paradigm-advisor after the migration brief and discovery specs exist so it can produce the paradigm_decision.md artifact.

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 like domain models, architecture documents, and process flows for signals such as aggregates, inheritance, immutability, or event queues. This Skill classifies the paradigm as procedural, OO, functional, event-driven, or hybrid with citable evidence and confidence levels.

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

Node.js is naturally event-driven and asynchronous, Go favors CSP-style concurrency with goroutines, and Rust leans toward ownership-based functional async. The bundled paradigm catalog maps common stacks to their natural paradigms plus viable alternatives.

What inputs does the paradigm advisor need to run?▼

It requires a migration brief declaring the target stack and a populated _reversa_sdd/ directory with domain, architecture, and inventory specs. It operates entirely on specifications and never reads legacy source code.

What happens when the legacy and target paradigms differ?▼

The Skill presents at least four concrete gap implications with examples from the legacy system, then offers three options: adopt the target paradigm, force the legacy paradigm, or use a hybrid. The human user always makes the final choice.

Can the paradigm decision be made automatically without user input?▼

No. The Skill never skips presenting the three options and never records a decision without the user's justification. In non-interactive environments it writes a pending_decisions.md file and waits for human review.