What problem does it solve? Migrating a legacy system requires explicit, traceable design decisions about topology, bounded contexts, domain models, and data migration. This Skill structures that work into a two-phase process with mandatory human approval gates, preventing silent 1-to-1 decomposition and undocumented architectural choices. ## Core Features & Use Cases - Topology Decision (Phase 1): Detects the legacy topology, diagnoses structural health, always proposes a modern alternative, and records the user's choice in topology_decision.md with a human approval pause. - Target System Specs (Phase 2): Produces target_architecture.md (with Mermaid diagram), target_domain_model.md, target_data_model.md, and data_migration_plan.md, all honoring the chosen paradigm (event-driven, OO with DI, functional, actor model, or procedural). - Full Traceability: Every new element maps back to the legacy system or to discard_log.md, with explicit justification for every merge, split, or removal. - Use Case: As the fourth agent of a migration team, invoke it after the Strategist confirms a migration strategy to turn business rules and legacy analysis into concrete architecture and data migration specs. ## Quick Start Run /reversa-designer after the migration strategy is approved to detect the legacy topology and design the target architecture, domain model, and data migration plan.
