Verified:GitHub

reversa

Orchestrate sequential reverse engineering of legacy systems into executable specifications.

Updated May 13, 2026

Search Tags:#agent orchestration #spec generation #checkpointing #legacy modernization #reverse engineering #documentation depth #policy-driven development

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reversa orchestrates reverse engineering of a legacy system into executable, audit-defensible specifications that AI agents can follow reliably.

Core Features & Use Cases

Legacy system mapping: Reads and interprets the current project state, producing a plan for downstream extraction agents.
Sequential multi-agent orchestration: Runs the correct Reversa agents in order, checkpointing progress between phases to support resumability.
Spec depth control: Prompts the user to choose documentation level (Essential, Complete, Detailed) before generating specs.

Quick Start

Use Reversa by typing to the chat: /reversa.

Frequently Asked Questions about reversa

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

FAQPage Schema

How do I convert legacy code into executable specs for AI agents?▼

To convert legacy code into executable specs for AI agents, Reversa orchestrates reverse engineering of your system, producing audit-defensible specifications with sequential execution and checkpointing for reliable downstream agent use.

What is the best way to reverse engineer a legacy system into documentation?▼

The best way to reverse engineer a legacy system is using an orchestration process that reads your project state, generates a sequential extraction plan, and prompts you to choose documentation depth (Essential, Complete, or Detailed) before generating specs.

How do I start agent orchestration for legacy modernization?▼

To start agent orchestration for legacy modernization, initiate the Reversa workflow to map your project, execute extraction agents sequentially, and enforce blocking user approval checkpoints between phases to ensure audit-defensible progress.

Can I resume a reverse engineering workflow after stopping?▼

Yes, you can resume a reverse engineering workflow because Reversa uses checkpointing with a state.json file and updates a plan.md file, allowing you to resume sequential multi-agent execution from the last completed phase without losing progress.

Does multi-agent spec generation support parallel execution?▼

No, multi-agent spec generation does not support parallel execution; Reversa enforces sequential, non-parallel plan execution with blocking user approval checkpoints to maintain audit-defensible specifications and reliable state tracking.

Do I need to manually track state during legacy code documentation?▼

No, you do not need to manually track state during legacy code documentation because Reversa automatically updates .reversa/state.json and .reversa/plan.md, applying checkpointing logic to manage resumable workflows across sequential phases.