reversa-extract-soul

Generate a soul.md Spec from surface.json summarizing legacy codebase purpose and entities.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-extract-soul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-extract-soul
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/skills/reversa/reversa-extract-soul
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-extract-soul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts scattered legacy project signals into an executive-ready “soul” document that explains what the system is, what its essential data skeleton likely is, and which foundational decisions shaped it—without doing full excavation or deep business-rule analysis.

Core Features & Use Cases

  • One-file system synthesis: Produces a single output artifact, <output_folder>/soul.md, focused on purpose, core entities, and foundational decisions.
  • Evidence-first distillation: Uses surface.json from the Scout plus light sampling of relevant domain/stack artifacts, marking any uncertainty as 🟡 or 🔴.
  • Non-destructive output behavior: Avoids overwriting an existing soul.md and instead guides you to keep it or create a timestamped version.
  • Manual executive invocation: Designed to run shortly after the Scout for quick overview, rather than replacing Archaeologist/Detective deep work.

Quick Start

Run reversa-extract-soul to generate the soul Spec at <output_folder>/soul.md from the already-created .reversa/context/surface.json.

Frequently Asked Questions about reversa-extract-soul

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

FAQPage Schema
How do I generate an executive overview from a legacy codebase for architecture discovery?

To generate an executive overview, distill legacy intent into a single Spec document that describes system purpose, core entities, and foundational decisions using sampled domain artifacts and git history analysis.

What is domain modeling synthesis for legacy modernization and when do I need it?

Domain modeling synthesis for legacy modernization extracts the essential data skeleton and foundational decisions of a system, needed when you require a lightweight executive summary rather than full module-by-module excavation.

How to extract a system spec from surface.json after initial codebase scanning?

To extract a system spec from surface.json, run the synthesis process to read the context file, sample relevant domain artifacts, analyze git log history, and output a single soul.md document capturing purpose and entities.

Can I safely regenerate a soul.md file without overwriting my existing architecture documentation?

You cannot automatically overwrite an existing soul.md file; the extraction process enforces non-overwrite safety by guiding you to either keep the current version or generate a timestamped copy to preserve architecture documentation.

Does this legacy spec synthesis approach replace deep codebase excavation tools?

Legacy spec synthesis does not replace deep excavation tools; it provides a quick executive synthesis of purpose and core entities, designed for manual overview rather than detailed business-rule or Archaeologist-level analysis.

What do I need to create a soul spec document for a legacy codebase?

To create a soul spec document, you need the prior output of a Scout process stored as `.reversa/context/surface.json`, which provides the foundational surface-level context for extracting system intent and core entities.