reversa-designer

A legacy system migration requires a two-phase design workflow that first detects the existing topology and then proposes a modern architecture with bounded contexts, domain models, and a data migration plan. This Skill executes that workflow by generating topology_decision.md for approval before proceeding to detailed architecture artifacts.

Topology detection is the process of mapping your existing legacy system structure to inform a modern alternative proposal. You need it during the first phase of a reverse migration to ensure the target architecture maintains full traceability to the source system before any domain or data modeling begins.

Mapping bounded contexts involves grouping legacy rules into discrete domains and translating them into a target domain model. This Skill automates that grouping and generates target_domain_model.md to ensure alignment and traceability with your overall migration strategy and target architecture.

Yes, generating a data migration plan with traceability is a core output of this Skill. It produces data_migration_plan.md alongside target_data_model.md, recording evidence and decisions in the _reversa_sdd workspace to ensure full auditability throughout the migration process.

Yes, the workflow enforces a human pause for approval after Phase 1. It generates topology_decision.md detailing the legacy topology and proposed modern alternative, and waits for your approval before executing Phase 2 to deliver the target architecture, domain, and data models.

A complete reverse migration design requires topology_decision.md, target_architecture.md, target_domain_model.md, target_data_model.md, and data_migration_plan.md. This Skill generates all five artifacts with full traceability to the legacy system, documenting evidence in the _reversa_sdd workspace for auditability.