reversa-coding

Executes actions.md plans into code with parallel-aware, phased progression and generates audit trail artifacts.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-coding-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-coding
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-coding
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-coding-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduz a execução do actions.md em código. Atualiza checkboxes para [X], escreve progress.jsonl, gera legacy-impact.md e regression-watch.md. Use quando o usuário digitar "/reversa-coding", "reversa-coding", "executar plano" ou pedir para começar a codar a feature ativa. Último skill do ciclo forward, depois de /reversa-to-do (e opcionalmente /reversa-audit ou /reversa-quality).

Core Features & Use Cases

  • Conduz a execução do actions.md em código fase por fase, respeitando paralelismo e dependências.
  • Gera os artefatos auditáveis legacy-impact.md e regression-watch.md para auditoria futura.
  • Integra-se com a pipeline reversa para manter consistência entre legado e código.

Quick Start

Inicie a conversão executando /reversa-coding para transformar actions.md em código executável.

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 plan into executable code phase by phase?

To execute actions.md into code, you apply deterministic phases like Preparation, Tests, Core, Integration, and Polishing while respecting dependencies and parallelism to generate progress.jsonl.

Why do I need an existing pipeline state to generate code from a markdown plan?

Generating code requires an existing pipeline state like .reversa/state.json to safely track artifacts and maintain consistency between legacy impact and the newly written code.

How do code generation workflows maintain audit trails for future regression testing?

Code generation workflows maintain audit trails by generating legacy-impact.md and regression-watch.md files during execution, which document legacy changes for future verification.

What preconditions are required before converting a markdown plan into code?

Before converting a markdown plan into code, preconditions such as the presence of _reversa_sdd with architecture.md and domain.md must be met to ensure safe generation.

Can I use deterministic code generation to track legacy impact and regression watch artifacts?

Yes, deterministic code generation specifically tracks legacy impact and regression watch artifacts by updating checkboxes to [X] and writing progress.jsonl during the execution phases.

What is the best way to start coding a feature from a structured actions plan?

The best way to start coding a feature from a structured actions plan is to trigger the forward execution cycle, which processes the plan phase by phase to output executable code.