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 syntax change end up with broken mental models. 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 (procedural, OO classic, OO with DI, functional, event-driven, actor model, dataflow, hybrid) using evidence from _reversa_sdd/ artifacts with confidence tagging (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 real rules and flows from the legacy system. - Decision Recording: Presents three options (adopt natural paradigm, force legacy paradigm, hybrid), collects the user's choice, and writes paradigm_decision.md with a derived appetite (conservative, balanced, transformational) for downstream agents. - Use Case: A team migrating a Rails monolith to Node.js runs this Skill first; it detects OO classic with Active Record, infers event-driven as Node's natural paradigm, and documents the user's choice so the Curator, Strategist, Designer, and Inspector agents honor it. ## Quick Start Run /reversa-paradigm-advisor after the migration brief exists to analyze the legacy paradigm and record the paradigm decision for the migration team.