Generate migration design specifications from legacy system topology.
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-designer-rdinda
Please help me install this Agent Skill. Skill: reversa-designer Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-designer Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-designer-rdinda
It turns legacy system findings into a complete, traceable target design so a migration team can move forward without losing accountability to the original data and rules.
Use the reversa-designer skill by invoking /reversa-designer to generate a topology decision first, then approve it so it can produce the target architecture, domain model, data model, and data migration plan.
High-intent search queries and answers about installing and using this skill.
To design a target architecture for legacy system migration, generate a topology decision first, then approve it to produce target architecture, domain model, data model, and a data migration plan with full traceability to legacy origins.
Traceability in domain modeling ensures every new architectural element links back to specific legacy origins or is explicitly discarded and logged, maintaining accountability to original data and rules during system migration.
Yes, you can model event-driven, OO with DI, functional, actor model, or dataflow paradigms. The chosen target paradigm is explicitly materialized into the architecture and domain models during migration planning.
The best way to plan ETL for staged migration is to confirm topology and paradigm decisions first, then generate a deterministic data migration plan aligned with the target data model and domain architecture.
To produce bounded contexts before architecture modeling, you need to provide multiple migration briefs and artifacts so the system can detect legacy topology and enforce traceability rules across the domain model.
Migration design requires topology approval because the staged workflow enforces human confirmation of topology and paradigm decisions before proceeding to generate architecture, domain models, and data models.
AlexandrePontesjrGenerate target architecture, domain model, data model, and ETL migration plan from legacy topology.
saolalabDesign ETL pipelines for batch and incremental data ingestion.
stribusPlan migration topology and generate architecture decision documents for legacy systems.
afsjrGenerate target architecture and data migration plan from legacy topology.
