What problem does it solve? It turns a structured implementation plan (actions.md) into actual code changes while preserving traceability against a reverse-engineered legacy baseline, so every modification to legacy behavior is documented and watchable for regressions. ## Core Features & Use Cases - Phased plan execution: Runs 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 auditing: Generates legacy-impact.md mapping touched files to components from the reverse extraction, classifying impact type and severity, and listing preserved versus modified rules. - Regression watch tracking: Creates regression-watch.md with stable watch item IDs for modified or removed rules, feeding future re-extraction cycles. - Use Case: After running the reverse pipeline and /reversa-to-do on a legacy codebase, invoke this skill to implement the planned feature while automatically producing an audit trail of what legacy behavior changed and what must keep holding true. ## Quick Start Type /reversa-coding to execute the pending actions in the active feature plan and generate the legacy impact and regression watch reports.
