reversa

Reverse engineering a legacy system involves orchestrating an end-to-end workflow that coordinates planning phases and agent execution to produce executable specifications. It eliminates the complexity of initiating analysis by guiding the sequence of system mapping and spec generation.

Agent orchestration for legacy codebase mapping works by coordinating child skills sequentially, running a Scout and Archaeologist sequence. It enforces step ordering, records checkpoints, and marks progress in a plan file to ensure structured analysis.

Yes, you can resume a reverse engineering analysis session. The workflow reads and updates a state file to apply session resumption, allowing you to pick up from the last recorded checkpoint without losing prior mapping progress.

You select documentation granularity after the initial Scout phase completes. The workflow presents a standardized menu offering Essential, Complete, or Detailed levels, then persists your chosen documentation level in the state configuration.

The best way to organize generated specifications is to execute a dedicated organization step for granularity and layout before invoking the Archaeologist. This configuration is saved persistently in a TOML config file.