reversa-designer

Generate target architecture, domain model, data model, and ETL migration plan from legacy topology.

Updated May 5, 2026
One-click install
npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-designer-alexandrepontesjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-designer
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-designer
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-designer-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates guesswork in migration by turning legacy topology and rules into concrete, traceable target architecture and data/domain specifications.

Core Features & Use Cases

  • Legacy topology detection and modernization proposal: identifies the legacy organization, diagnoses structural health, and proposes a modern alternative with explicit options.
  • Two-phase spec generation with human approval gate: Phase 1 produces topology_decision.md and pauses for user approval; Phase 2 generates target_architecture.md, target_domain_model.md, target_data_model.md, and data_migration_plan.md with full traceability.
  • Paradigm- and strategy-aware design: honors the chosen paradigm from paradigm_decision.md and the confirmed migration_strategy.md, ensuring bounded contexts and designs align with event-driven, OO+DI, functional, actor model, or dataflow expectations.

Quick Start

Run reversa-designer so it generates _reversa_sdd/migration/topology_decision.md, then wait for the user to approve option 1, 2, or 3 before producing the target architecture, domain model, data model, and migration plan.

Frequently Asked Questions about reversa-designer

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

FAQPage Schema
How do I design a target architecture and domain model from a legacy system?

Designing a target architecture from a legacy system requires parsing prerequisite topology and migration briefs to generate modern bounded contexts, data schemas, and Mermaid-based architecture documentation with full traceability.

What is the best way to plan an ETL data migration with bounded contexts?

Planning an ETL data migration with bounded contexts involves creating a migration plan that explicitly maps legacy artifacts to new domain structures or a discard log, ensuring strict adherence to a confirmed architectural paradigm.

How does the two-phase migration design process with an approval gate work?

The two-phase migration design process works by first generating a topology decision file and pausing for explicit human approval, then producing the target architecture, domain model, data model, and migration plan.

Can I generate data models and migration plans for event-driven architectures?

Yes, you can generate data models and migration plans for event-driven architectures because the design process honors the chosen paradigm from prerequisite artifacts, ensuring bounded contexts align with specific architectural expectations.

Do I need prerequisite software design documents before generating target architecture?

Yes, you need prerequisite software design documents because the target architecture generation requires parsing prior artifacts like paradigm decisions and confirmed migration strategies to ensure strict design adherence.

How to map legacy artifacts to new data schemas during a system migration?

Mapping legacy artifacts to new data schemas during a system migration requires an ETL-focused migration plan that defines data constraints and explicitly logs unmapped legacy items to a discard log for traceability.