What problem does it solve? Migrating a legacy system to a new language or framework often hides a deeper shift in programming paradigm (procedural, OO, functional, event-driven), which teams discover too late. 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 as procedural, OO, 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 target paradigm, force legacy paradigm, hybrid) and writes a structured paradigm_decision.md artifact consumed by downstream migration agents. - Use Case: When migrating a Rails monolith to Node.js, the Skill detects classic OO with Active Record, infers event-driven as Node's natural paradigm, explains implications like synchronous flows becoming sagas, and records the user's chosen strategy. ## 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.
