reversa-curator

Convert legacy specifications into migration-ready business rules with human review decisions.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-curator-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-curator
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-curator-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reversa transforma regras e comportamentos do legado em especificações executáveis por agentes, mas precisa separar o que é regra de negócio do que é artefato técnico do sistema antigo; este agente resolve isso com decisão rastreável e deixa pendências para humanos quando necessário.

Core Features & Use Cases

  • Inventaria regras do legado a partir de specs consolidadas em _reversa_sdd/ (requirements/design por unit + artefatos de domínio e análise de código) e relaciona com gaps e perguntas.
  • Aplica uma política determinística de decisão (MIGRAR, DESCARTAR ou DECISÃO HUMANA) priorizando ambiguidade e lacunas para revisão humana.
  • Gera artefatos de saída de migração em _reversa_sdd/migration/, incluindo target_business_rules.md, discard_log.md e atualização de ambiguity_log.md.
  • Rastreia origem e justificativa: cada item mantém referência ao arquivo/seção de origem e, quando descartado, documenta vínculo com mudança de paradigma.

Quick Start

Use o agente para executar a ativação /reversa-curator no contexto do seu projeto de migração, garantindo que migration_brief.md e paradigm_decision.md existam em _reversa_sdd/migration/.

Frequently Asked Questions about reversa-curator

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

FAQPage Schema
How do I decide what business rules to migrate or discard from legacy systems?

To decide what business rules to migrate or discard from legacy systems, a curator policy evaluates consolidated legacy specifications and flags items to migrate, discard, or escalate for human review. This generates traceable target business rules and a discard log with justifications.

What is legacy specification curation for agent workflows?

Legacy specification curation for agent workflows is the process of separating executable business rules from technical artifacts in old systems. It transforms legacy specifications into migration-ready rules while maintaining source traceability and logging ambiguities for human decisions.

How do I handle ambiguity or gaps when migrating legacy business rules?

To handle ambiguity or gaps when migrating legacy business rules, the curation process applies a mandatory human decision policy. It updates an ambiguity log with pending items, ensuring unresolved lacunas are escalated for human review rather than being automatically migrated or discarded.

Do I need a migration brief and paradigm decision to start curating legacy rules?

Yes, you need a migration brief and paradigm decision files in your project directory to start curating legacy rules. These inputs provide the necessary context for the curator to evaluate requirements, domain artifacts, and code analysis before generating target business rules.

How do I trace the origin of discarded business rules during a system migration?

To trace the origin of discarded business rules during a system migration, the curation process maintains a reference to the source file and section for each item. When a rule is discarded, the discard log documents the justification and links it to the paradigm change.