skills.rest
maximoseo
maximoseoCOMMUNITY
Explore all skills by this author →
GitHub

reversa-designer

Analyze legacy systems and document migration architectures with traceability.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes legacy architectures to plan and document a migration path, then creates a modern topology and artifact blueprint with full traceability to the legacy.

Core Features & Use Cases

  • Detects legacy topology and architectural health to inform safe migration.
  • Recommends a modern topology aligned with the declared migration brief, chosen paradigm, and migration strategy, plus a bounded-context outline.
  • Produces migration artifacts in _reversa_sdd/migration/ including topology_decision.md, target_architecture.md, target_domain_model.md, target_data_model.md, and data_migration_plan.md, all with traceability to legacy assets.
  • Supports a two-phase workflow: Phase 1 decides topology (with human approval) and Phase 2 materializes architecture, domain, and data models.

Quick Start

Invoke the designer with /reversa-designer to begin Phase 1 topology decision.

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 legacy system migration architecture with traceability?▼

A legacy system migration architecture is planned by analyzing the existing topology and proposing a modern target with explicit traceability to legacy assets. This Skill generates a two-phase blueprint with bounded contexts, Mermaid diagrams, and ADR-style decisions.

What is a two-phase migration topology workflow?▼

A two-phase migration topology workflow separates topology decisions from detailed architecture design. Phase 1 decides the modern topology requiring human approval, while Phase 2 materializes the target domain model, data model, and data migration plan.

How do I document bounded contexts and domain models for a system migration?▼

Document bounded contexts and domain models for a system migration by generating artifacts like target_domain_model.md and target_data_model.md. These files map the modern domain structure while maintaining explicit traceability to the analyzed legacy architecture.

Does this migration architect support Mermaid diagrams and ADR-style decisions?▼

Yes, the migration architect supports Mermaid diagrams and ADR-style decisions to document topology choices. It outputs structured markdown files in a migration directory to capture architectural decisions and visual topology representations.

When do I need a data migration plan with legacy asset traceability?▼

You need a data migration plan with legacy asset traceability when modernizing legacy systems to ensure no critical data structures are lost. It is required when mapping a legacy data model to a new target data model across a structured two-phase migration workflow.

Related Skills

Explore More Software Engineering Skills→
cliffthelincliffthelin

reversa-designer

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

Community
Advanced
ricardops34ricardops34

reversa-designer

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

Community
Advanced
AndreJorgeLopesAndreJorgeLopes
1

update-visualizations

Update Mermaid architecture and workflow diagrams from recent Git changes.

Community
Intermediate
Pabloprogramador23Pabloprogramador23

reversa-designer

Plan and execute a two-phase migration design from legacy to modern architecture.

Community
Advanced