reversa-architect

Generate C4 diagrams, ERD, integration maps, and spec impact matrices from legacy analysis.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-architect-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-architect
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-architect
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-architect-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a legacy codebase into a coherent, decision-ready architecture report by consolidating discovered artifacts into diagrams, ERD, integration maps, and spec impact coverage.

Core Features & Use Cases

  • C4 architecture diagrams: Produces C4 Context, Containers, and Components (as configured by documentation level).
  • Full ERD mapping: Generates a complete entity-relationship model with cardinalities and keys.
  • Integration and impact traceability: Documents external integrations and creates a Spec Impact Matrix to show what parts of the architecture are affected by which specs.
  • Technical debt synthesis: Identifies duplicated code, inconsistent patterns, outdated critical dependencies, and missing tests in critical modules.

Quick Start

Use the reversa-architect skill after running reversa-detective, ensuring .reversa/state.json points to the correct output_folder and that you set doc_level to completo to generate containers, components, ERD, and the Spec Impact Matrix.

Frequently Asked Questions about reversa-architect

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

FAQPage Schema
How do I generate complete architectural documentation for a legacy codebase?

Generate complete architectural documentation for a legacy codebase by synthesizing discovered artifacts into C4 diagrams, full ERD, integration maps, and spec impact coverage. This consolidates legacy project analysis into a coherent, decision-ready architecture report.

What is a spec impact traceability matrix and when do I need one?

A spec impact traceability matrix maps which parts of the architecture are affected by specific specifications. You need this during architectural documentation to ensure full spec-to-component impact coverage and maintain decision-ready oversight of legacy systems.

How do I map external integrations and database schemas when analyzing a legacy project?

Map external integrations and database schemas by generating complete entity-relationship models with cardinalities and keys, alongside external integration mapping. This synthesizes legacy project analysis into comprehensive architectural artifacts.

Can I generate C4 context, containers, and components diagrams automatically for an existing project?

Yes, you can generate C4 context, containers, and components diagrams automatically by setting the documentation level to 'completo'. This produces the required Markdown artifacts under your selected output folder during the interpretation phase.

What is the best way to document technical debt across critical software modules?

The best way to document technical debt is by synthesizing analysis to identify duplicated code, inconsistent patterns, outdated critical dependencies, and missing tests in critical modules. This consolidates findings into your architectural documentation.

Do I need to run discovery artifacts before generating architecture documentation?

Yes, you need to run discovery artifacts first. This skill applies during interpretation after discovery artifacts are produced, requiring a valid state file pointing to the correct output folder to generate the final architecture report.