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. ## Core Features & Use Cases - Paradigm Detection: Classifies the legacy system's paradigm from _reversa_sdd/ specification artifacts with confidence-tagged evidence (confirmed, inferred, gap, ambiguous). - Stack Mapping: Infers the natural paradigm of the declared target stack using a built-in catalog covering Node.js, Go, Rust, Elixir, Python, .NET, Java, Ruby, and more. - Guided Decision: Presents three concrete options (adopt target paradigm, force legacy paradigm, or hybrid) with at least four system-specific implications, then records the user's choice and derived appetite in paradigm_decision.md. - Use Case: When migrating a classic Rails monolith to an event-driven Node.js backend, run this agent first to surface how synchronous flows become asynchronous with retries and DLQs before any code is written. ## Quick Start Ask the agent to analyze the legacy specs in _reversa_sdd and produce a paradigm decision for the target stack declared in the migration brief.