skills.rest
afsjr
afsjrCOMMUNITY
Explore all skills by this author →
GitHub

reversa-designer

Generate target architecture and data migration plan from legacy topology.

Updated Mar 31, 2026
Search Tags:#migration#architecture design#traceability#data model#domain model#bounded contexts#topology decision
One-click install
npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-designer-afsjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-designer
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-designer
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-designer-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns legacy-system topology and domain/data evidence into a modern target architecture plus a traceable migration plan, while enforcing explicit topology approval and preventing 1-to-1 decomposition.

Core Features & Use Cases

  • Two-phase migration design: runs topology detection and proposal in Phase 1, then produces target architecture, domain model, data model, and migration plan in Phase 2 after human approval.
  • Topology-first with human gate: generates and requires topology_decision.md before any downstream artifacts, using .state.json as the single source of truth for approval.
  • Full traceability to the legacy: maps each element of the new system back to legacy sources or discard_log.md, with explicit provenance tables for domain and data.
  • Paradigm-aligned modeling: applies the chosen paradigm from paradigm_decision.md (e.g., event-driven, OO with DI, functional, actor model, procedural/dataflow) and ensures required checks via the paradigm checklist.

Quick Start

Invoke /reversa-designer (usually via /reversa-migrate) and wait for the Phase 1 topology approval before generating the target architecture, domain model, data model, and data 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 data migration plan from legacy system topology?▼

You can generate a modern target architecture and traceable data migration plan by feeding legacy topology and architecture evidence into a two-phase design process that enforces explicit topology approval before producing downstream artifacts.

How does topology decision gating work in a legacy migration architecture?▼

Topology decision gating requires generating a topology_decision.md file and updating a .state.json source of truth to enforce human approval before any downstream target architecture or data migration artifacts are produced.

How do I prevent 1-to-1 decomposition when migrating legacy domains?▼

You prevent 1-to-1 decomposition by enforcing bounded context decomposition rules that require paradigm-aligned domain modeling, ensuring new system elements do not simply mirror legacy structures one-to-one.

How do I maintain traceability to legacy systems during a data migration?▼

You maintain legacy traceability by generating explicit provenance tables that map each new domain and data model element back to legacy sources, while logging discarded elements in a discard_log.md file.

Can I apply different software paradigms like event-driven or functional models to my target architecture?▼

Yes, target architecture modeling can apply event-driven, OO with DI, functional, actor model, or procedural paradigms by reading a paradigm_decision.md file and validating the design against a paradigm checklist.

What artifacts do I need to produce a complete legacy to modern architecture migration plan?▼

Producing a complete migration plan requires generating topology_decision.md, target_architecture.md, target_domain_model.md, target_data_model.md, and data_migration_plan.md across two distinct design phases.

Related Skills

Explore More Software Engineering Skills→
RdindaRdinda
1

reversa-designer

Generate migration design specifications from legacy system topology.

Community
Advanced
stribusstribus
1

reversa-designer

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

Community
Advanced
ricardops34ricardops34

reversa-designer

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

Community
Advanced
cliffthelincliffthelin

reversa-designer

Detect legacy topology and generate auditable target architecture, domain, and data specifications.

Community
Advanced