reversa-designer

Plan migration topology and generate architecture decision documents for legacy systems.

1|Updated Nov 20, 2025

Search Tags:#architecture #migration #topology #data-model #bounded-contexts #domain-model

Ready to run

npx skills add https://github.com/stribus/pygerengastos --skill reversa-designer-stribus

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill facilita o design de migração de sistemas legados, capturando decisões de topologia, alinhando regras de negócio e mapeando dados, para manter rastreabilidade com o legado.

Core Features & Use Cases

Topologia de migração e decisão de arquitetura: orienta o time na escolha entre preservação, modernização ou híbrido, com justificativas e evidências.
Definição de bounded contexts e domínios: agrupa regras e modelos para o sistema novo com rastreabilidade de origem.
Geração de artefatos de migração: produz os documentos alvo (topology_decision.md, target_architecture.md, target_domain_model.md, target_data_model.md e data_migration_plan.md) com links para referências.
Rastreamento e conformidade: registra evidências de legado e decisões de design para auditoria.

Quick Start

Inicie a fase de decisão de topologia para o sistema legado e comece a gerar os artefatos de migração.

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 topology for legacy systems?▼

To plan migration topology for legacy systems, you evaluate preservation, modernization, or hybrid approaches with justifications and evidence, producing a topology_decision.md document to guide architecture choices.

What is the best way to maintain traceability during data migration planning?▼

Maintaining traceability during data migration planning involves generating a data_migration_plan.md that maps target data models back to legacy sources, ensuring alignment with the selected migration strategy and paradigm.

How do I define bounded contexts and domain models for a modernized architecture?▼

Defining bounded contexts and domain models for modernized architecture requires grouping business rules and generating a target_domain_model.md that maintains origin traceability links to the legacy system.

Can I document target data models and architecture decisions together?▼

Yes, you can document target data models and architecture decisions together by generating target_architecture.md and target_data_model.md artifacts that preserve alignment with the selected paradigm and migration strategy.

Why do I need to track legacy evidence and design decisions for migration?▼

Tracking legacy evidence and design decisions for migration is necessary to ensure auditability and compliance, recording justifications for topology choices and mapping rules across bounded contexts back to their origin.