reversa-designer

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Resolve a dificuldade de reconstruir um sistema legado em um novo modelo executável, transformando descoberta e decisões de migração em specs completas e rastreáveis.

Core Features & Use Cases

  • Topology decision: detecta a topologia do legado, propõe uma alternativa moderna e força aprovação humana antes de avançar.
  • Target architecture & models: gera arquitetura alvo (com diagrama), domain model alvo e data model alvo com rastreabilidade para o legado.
  • Plano de migração de dados: produz um plano estruturado de ETL, cutover e validações, alinhado ao paradigma e à estratégia confirmada.
  • Rastreabilidade total: cada elemento do novo aponta para origem no legado ou para descarte documentado.

Quick Start

Use o reversa-designer ao iniciar a migração com o comando /reversa-designer para produzir topology_decision.md e aguardar sua aprovação antes de desenhar a arquitetura alvo.

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 system architecture from legacy reverse-engineering artifacts?

To design a target system architecture from legacy artifacts, this skill reads mandatory migration SDD inputs and generates a modern architecture, domain model, and data model with full traceability to the legacy system or discard log.

How does the migration workflow enforce topology approval before generating bounded contexts?

The migration workflow enforces topology approval by detecting the legacy topology, proposing an alternative, and requiring human approval via a .state.json file before materializing bounded contexts and data mappings.

What is the best way to generate a structured ETL plan for a system migration?

The best way to generate a structured ETL plan is by applying a confirmed migration strategy and paradigm decision, which produces a comprehensive data migration plan covering ETL, cutover, and validations.

Do I need to provide a migration SDD input for domain modeling and data model mapping?

Yes, you need to provide mandatory migration SDD inputs for domain modeling and data model mapping, as the skill requires reading these artifacts to generate outputs exclusively under the _reversa_sdd/migration/ directory.

When do I need to maintain traceability to a discard log during system migration?

You need to maintain traceability to a discard log during system migration when elements from the legacy system are not carried forward, ensuring every new architecture element points to its origin or documented discard.