Verified:GitHub

reversa-designer

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

Updated May 13, 2026

Search Tags:#domain modeling #governance #architecture design #traceability #data migration #bounded contexts #legacy modernization

Ready to run

npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-designer-cliffthelin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reconstructing a legacy system into a new, audit-defensible target architecture and data/domain specifications without losing traceability to the original intent.

Core Features & Use Cases

Phase 1 topology decisioning: Detects legacy topology, proposes a modern alternative, and produces topology_decision.md for human approval.
Phase 2 target blueprint generation: Produces target_architecture.md, target_domain_model.md, target_data_model.md, and data_migration_plan.md with explicit mapping back to legacy.
Paradigm- and strategy-aware design: Enforces the chosen paradigm from paradigm_decision.md and the user-confirmed migration strategy from migration_strategy.md.

Quick Start

Run the reversa-designer activation after Phase 1 prerequisites are available and approve the generated topology_decision.md before requesting Phase 2 artifacts.

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 for legacy modernization with traceability?▼

Legacy modernization architecture design with traceability detects existing topology, proposes modern alternatives, and generates auditable target domain and data specifications mapped back to the original system.

What is legacy topology detection and how does it support data migration planning?▼

Legacy topology detection analyzes existing system structures to propose modern alternatives, producing a topology decision document required for human approval before generating downstream data migration plans.

How do I generate a domain model and data migration plan for bounded contexts?▼

Generating domain models and data migration plans for bounded contexts requires an approved topology decision, producing target architecture, domain, and data specifications with explicit mapping back to legacy systems.

Do I need a migration strategy document before generating target architecture specifications?▼

Yes, target architecture generation requires a user-confirmed migration strategy document and a paradigm decision file to enforce the chosen paradigm and migration approach during system design.

Can I apply target domain modeling without approving the legacy topology decision first?▼

No, target domain modeling requires a two-phase control process where you must approve the generated topology decision document via a state file before requesting target blueprint generation.

Why does legacy modernization require a two-phase topology approval process?▼

Legacy modernization uses two-phase topology approval to ensure the proposed modern alternative aligns with strategic goals before generating detailed architectural, domain, and data migration specifications.