reversa-coding

To transform an execution plan into executable code with traceability, use a phased execution approach that processes actions from a documented actions.md plan and logs progression in a JSONL file for auditability. It also generates regression watch artifacts.

Phased dependency-aware code generation is an execution process that runs actions by phase—Preparation, Tests, Core, Integration, Polishing—while respecting dependencies. It executes independent subsets in parallel and stops when failures are detected.

You can generate audit artifacts and regression tracking files by executing your action plan through a structured coding workflow. This produces a legacy-impact.md file detailing legacy changes and a regression-watch.md file tracking what must remain true.

Yes, you need reverse engineering context files to execute a coding plan. The process strictly requires a reverse SDD directory containing architecture.md and domain.md files, otherwise it aborts without modifying the disk.

You track legacy impact and regression risks when applying code changes by generating dedicated markdown artifacts. The workflow creates a legacy-impact.md file to record what changed and a regression-watch.md file to monitor what needs to stay true.