reversa-designer

Detect legacy topology and design migration-ready target specifications with traceability.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-designer-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-designer
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-designer
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-designer-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reversa-designer converts undocumented legacy knowledge into operational, traceable target specifications that AI coding agents can safely use to evolve a system without breaking existing behavior.

Core Features & Use Cases

  • Two-phase migration design: performs topology detection with human approval, then produces target architecture, domain model, data model, and a data migration plan.
  • Modern topology proposal + choice: always detects the legacy structure, proposes a modern alternative, presents 3 options (preserve/modernize/hybrid), and records the user decision.
  • Paradigm-aware design and zero silent changes: honors the chosen paradigm in paradigm_decision.md and prevents architecture/domain/data generation until topology is approved.
  • Total traceability: every new system element links back to legacy sources or an explicit discard log.

Quick Start

Activate reversa-designer with /reversa-designer to detect legacy topology and produce topology_decision.md for 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 generate target system specifications from a legacy codebase?

You can generate migration-ready target system specifications by detecting legacy topology, proposing modern alternatives, and designing target architecture, domain models, and data migration artifacts with full traceability. This converts undocumented legacy knowledge into operational specs for AI coding agents.

What is the best way to ensure legacy traceability during architecture migration?

Legacy traceability is ensured by explicitly mapping each new system element, such as bounded contexts and aggregates, back to legacy sources or an explicit discard log. This prevents silent changes and maintains strict procedural alignment during system migration.

How does two-phase migration design work for domain modeling and ETL planning?

Two-phase migration design performs legacy topology detection with human approval gating first, then generates target architecture, domain models, data schemas, and ETL cutover steps. This enforces paradigm alignment and prevents generation until topology is approved.

Can I preserve my existing legacy topology instead of modernizing the architecture?

Yes, you can preserve your existing legacy topology. The system detects the legacy structure, proposes a modern alternative, and presents three options: preserve, modernize, or hybrid. Your decision is recorded before target architecture generation proceeds.

Do I need a confirmed migration strategy before designing bounded contexts and data schemas?

Yes, a migration brief, paradigm decision, and confirmed migration strategy are required inputs. These prerequisites are transformed into bounded contexts, aggregates, schemas, constraints, and ETL cutover steps for the new system.