reversa-architect

Synthesize legacy system findings into architectural documentation with C4 diagrams and ERD.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-architect-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-architect
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-architect
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-architect-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesizes a legacy project's findings into complete architectural documentation, including C4 diagrams, a full ERD, an integration map, and a Spec Impact Matrix.

Core Features & Use Cases

  • Generate end-to-end architectural documentation from reverse engineering artifacts.
  • Produce C4 context, containers, components, ERD, and traces for system integrations.
  • Use case: after the reverse-detective phase, distill findings into shareable architecture docs.

Quick Start

Run the Architect to synthesize findings into a complete architectural report.

Frequently Asked Questions about reversa-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate C4 diagrams and ERD from reverse-engineered legacy code?

Generate C4 diagrams and ERD from legacy code by synthesizing reverse-engineering findings into a cohesive architectural documentation set, producing context, containers, components, and integration maps.

What is the best way to document legacy system architecture after reverse engineering?

Documenting legacy system architecture involves distilling reverse-engineered findings into shareable artifacts like C4 diagrams, an ERD, and an integration map to provide a complete and cohesive overview.

Can I control the depth of architectural documentation generated for my project?

You can control documentation depth using the doc_level setting, which determines whether the output includes only essential architecture and context files or expands to detailed containers, components, and ERD artifacts.

Does this approach produce deployment guidance for legacy systems?

Yes, synthesizing legacy architecture produces deployment guidance when relevant, alongside essential architecture.md and c4-context.md files, ensuring comprehensive interpretation of the reverse-engineered system.

What inputs do I need to synthesize legacy architecture into complete docs?

To synthesize legacy architecture into complete docs, you need artifacts from a prior reverse-engineering or analysis phase, which are then distilled into an architectural report with C4 diagrams and integration maps.