reversa-designer

Plan and execute a two-phase migration design from legacy to modern architecture.

Updated Jun 6, 2026

Search Tags:#architecture #traceability #topology #bounded-context #domain-model #reverse-migration

Ready to run

npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-designer-pabloprogramador23

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-designer
Source: https://github.com/Pabloprogramador23/loja/tree/main/.agents/skills/reversa-designer
Command: npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-designer-pabloprogramador23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides and executes a two-phase reverse migration design, producing topology decisions and concrete artefacts to migrate legacy systems to a modern architecture with traceability to the source.

Core Features & Use Cases

Topology decision in two phases: Phase 1 detects legacy topology and proposes a modern alternative, with human pause for approval.
Artifact generation: Creates topology_decision.md, target_architecture.md, target_domain_model.md, target_data_model.md, and data_migration_plan.md with traceability to legacy.
Bounded contexts & domain modeling: Groups rules into bounded contexts and maps them to the new model, ensuring traceability and alignment with migration strategy.
Two-phase workflow: Phase 1 handles topology; Phase 2 handles architecture, domain and data.

Quick Start

Trigger the reverse-migration designer for Phase 1 to produce topology_decision.md and await approval.

Frequently Asked Questions about reversa-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan a migration from a legacy system to a modern architecture?▼

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.

What is topology detection and when do I need it for reverse migration?▼

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.

How do I map bounded contexts and domain models during a system migration?▼

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.

Can I generate a data migration plan with traceability to a legacy system?▼

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.

Does the migration design workflow require approval before generating architecture artifacts?▼

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.

What artifacts do I need for a complete reverse migration design?▼

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.