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.