What problem does it solve? It turns a structured implementation plan (actions.md) into actual code changes while preserving traceability to a legacy reverse-engineering extraction, so every modification to legacy behavior is documented and watchable for regressions. ## Core Features & Use Cases - Phased Plan Execution: Executes pending actions phase by phase (Preparação, Testes, Núcleo, Integração, Polimento), respecting dependencies and parallel markers, updating checkboxes and appending to progress.jsonl. - Legacy Impact Report: Generates legacy-impact.md mapping touched files to architecture components, classifying impact type and severity, and listing preserved versus modified business rules. - Regression Watch List: Creates regression-watch.md with stable watch item IDs so future reverse extractions can verify that changed or removed rules behave as expected. - Use Case: After running /reversa-to-do to produce an actions.md plan for a new feature on a legacy codebase, invoke this skill to implement the plan and automatically produce audit artifacts linking code changes back to documented legacy rules. ## Quick Start Type /reversa-coding to execute the pending actions in the active feature plan and generate the legacy impact and regression watch reports.
