Orchestrate phased reverse-engineering sessions with checkpoint-based state files.
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa
Please help me install this Agent Skill. Skill: reversa Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa
It coordinates a full reverse-engineering workflow that turns a legacy system into actionable, executable specifications for downstream AI agents.
.reversa/state.json to resume from where the process stopped, or to start first-run instructions..reversa/plan.md by splitting a generic step into per-module tasks once surface mapping is available..reversa/, _reversa_sdd/, and regression-watch history) and checkpointing to prevent context loss.Activate the reversa skill by asking your AI to run /reversa to start the end-to-end reverse-engineering and spec generation workflow for your legacy project.
High-intent search queries and answers about installing and using this skill.
Reverse engineering legacy systems into executable specs requires orchestrating a phased workflow that sequentially maps codebases and outputs AI-ready specifications. This process coordinates sequential agents to analyze modules and generate actionable documentation.
Yes, you can resume reverse engineering a legacy system after stopping because the workflow reads a state.json file to checkpoint progress. This state-driven execution allows you to restart exactly where the process previously halted without losing context.
You control documentation depth when reverse engineering code through a user-gated decision step that asks you to select an Essential, Complete, or Detailed level. This choice is persisted in configuration files to guide the final spec generation.
The best way to map legacy modules for AI agent execution is to run an initial Scout phase that performs surface mapping, then dynamically updates the plan. This splits generic steps into per-module tasks to guide deeper sequential analysis.
Limitations on where reverse engineering files are written enforce non-destructive behavior by restricting outputs to the .reversa directory and _reversa_sdd folders. These guardrails prevent the workflow from modifying your original source code.
stribusIdentify folders, languages, frameworks, dependencies, and entry points in legacy codebases.
jschulteAutomates implementing missing features from finalized specifications via Speckit workflows.
bejranondaAnalyze code complexity and detect code smells in multi-language codebases.
ChegginGenerate API references, user guides, and changelogs from code and git history.