What problem does it solve? Migrating a legacy system to a new stack often fails because teams treat it as a syntax change when it is actually a paradigm shift. This Skill detects the programming paradigm of a legacy system from its specification artifacts, infers the natural paradigm of the declared target stack, and forces a conscious, documented decision about 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). - Gap Analysis: Maps the legacy-to-target paradigm pair against a catalog of typical gaps and presents at least four concrete implications citing actual legacy rules and flows. - Decision Recording: Presents three options (adopt target paradigm, force legacy paradigm, hybrid) and writes the user's choice into paradigm_decision.md with a derived appetite (conservative, balanced, transformational) for downstream agents. - Use Case: When migrating a Rails monolith to Node.js, the Skill detects OO classic with Active Record, infers event-driven as Node's natural paradigm, and documents the user's decision on how to handle synchronous-to-async implications. ## Quick Start Run /reversa-paradigm-advisor after the migration brief exists to analyze the legacy paradigm and record a paradigm decision for the migration team.
