reversa-coding

Executes actions.md plans into code while generating legacy-impact and regression-watch audit artifacts.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-coding-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-coding
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.agents/skills/reversa-coding
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-coding-tjsasakifln

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a structured implementation plan (actions.md) into executed code changes with full traceability, recording progress, legacy impact, and regression watch items so nothing is lost between planning and auditing. ## 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, and updates checkboxes from [ ] to [X]. - Audit trail generation: Produces legacy-impact.md (mapping touched files to architecture components with severity) and regression-watch.md (stable-ID watch items for modified or removed rules). - Dual context anchoring: Works anchored on legacy extraction artifacts (architecture.md + domain.md) or greenfield artifacts (prd.md + SDD specs), aborting cleanly when neither exists. - Use Case: After running /reversa-to-do to build an action plan for a feature, invoke this skill to execute the plan, then hand legacy-impact.md and regression-watch.md to a future /reversa re-extraction cycle. ## Quick Start Type "/reversa-coding" or ask the agent to execute the active feature plan so it codes the pending actions and writes the progress and audit files.

Frequently Asked Questions about reversa-coding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an actions.md implementation plan with an AI agent?▼

Invoke /reversa-coding after generating the plan with /reversa-to-do. The skill runs pending actions phase by phase, marks checkboxes [X], logs progress.jsonl lines, and stops the phase if any action fails.

What is a regression-watch file in a spec-driven workflow?▼

It is a markdown table of watch items with stable IDs (W001, W002...) tracking rules that were modified or removed during implementation. Future reverse-extraction runs use it to verify those rules still hold, catching regressions early.

Can reversa-coding run on a greenfield project without legacy code?▼

Yes. If _reversa_sdd/ contains prd.md and at least one SDD spec instead of architecture.md and domain.md, the skill anchors on those artifacts and adapts legacy-impact.md and regression-watch.md accordingly.

Why does reversa-coding abort before writing any files?▼

It aborts when active-requirements.json is missing, actions.md is missing, or no context anchor exists in _reversa_sdd/. In that case it writes nothing to disk and tells you which pipeline (/reversa, /reversa-new, /reversa-requirements, or /reversa-to-do) to run first.

How do I run only part of the plan, like one phase or action range?▼

Pass a free-text scope argument such as "só Núcleo" or "T001-T005" when invoking the skill. It restricts execution to that scope instead of running all pending actions in order.