What problem does it solve?
It solves the problem of transforming a forward “to-do” action plan into real, phase-by-phase implementation code while keeping legacy consistency and producing audit artifacts.
Core Features & Use Cases
- Executes actions into code: Converts
feature-dir/actions.md unfinished items into working implementation, updating each checkbox as it succeeds.
- Maintains execution traceability: Appends immutable status entries to
feature-dir/progress.jsonl, including timestamps and files touched.
- Creates legacy audit trails: Generates
legacy-impact.md (what changed in the legacy vs what remains true) and regression-watch.md (what must be re-validated to prevent regressions), tied to _reversa_sdd/domain.md and _reversa_sdd/architecture.md.
- Applies phase scoping & dependency handling: Runs actions by phase (Preparação, Testes, Núcleo, Integração, Polimento) and respects independent action groups and flagged sub-conjuntos.
- Guardrails via hard preconditions: Refuses to run unless the reversa extraction exists and includes required legacy artifacts (
_reversa_sdd/architecture.md and _reversa_sdd/domain.md), preventing orphan audit outputs.
Quick Start
Run /reversa-coding to execute the current active feature’s actions into code and generate legacy-impact.md and regression-watch.md from the reversa-extracted legacy context.