Curate legacy business rules into migration-ready decisions from SDD artifacts.
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-curator
Please help me install this Agent Skill. Skill: reversa-curator Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-curator Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-curator
Ele organiza regras do legado em decisões claras (migrar, descartar ou levar para decisão humana), reduzindo retrabalho e garantindo rastreabilidade das fontes.
_reversa_sdd/, no migration_brief.md e no paradigm_decision.md.ambiguity_log.md.target_business_rules.md e discard_log.md com justificativas e vínculos a paradigma quando aplicável.Envie o comando /reversa-curator para que o agente gere target_business_rules.md e registre descarte e ambiguidades com base nas specs do legado.
High-intent search queries and answers about installing and using this skill.
To decide which legacy business rules to migrate, discard, or send for human review, you can curate SDD artifacts against a migration brief and paradigm mapping. This classifies each rule into migrate, discard, or human decision cases while maintaining traceability to source documents.
Tracking ambiguous business rules during a system migration is best handled by logging items marked with warnings or critical flags into an ambiguity log. The process sends these unresolved items for human decision-making while providing recommendations and maintaining a record of gaps.
Paradigm mapping affects legacy business rule migration by linking target rules to the chosen target paradigm. The curation process evaluates rules from SDD artifacts against the paradigm decision, ensuring generated target business rules align with the new architectural model.
Yes, you need an SDD and migration brief before curating business rules. The process explicitly requires reading prerequisite files like SDD artifacts, the migration brief, and the paradigm decision document to enforce the decision policy ordering and produce accurate migration outputs.
To generate a discard log with justifications for unused legacy rules, curate your legacy documentation against the migration brief. The process produces a discard log file that records discarded rules alongside their justifications and links to the target paradigm when applicable.
Some migrated business rules are flagged for human decision instead of automatic migration due to detected ambiguities or gaps in the legacy SDD artifacts. The curation policy identifies these unresolved items and routes them to an ambiguity log with recommendations rather than forcing an automated choice.
sandecoConvert legacy specifications into migration-ready business rules with human review decisions.
Pabloprogramador23Detect legacy paradigms from specs and guide migration decisions.
cliffthelinClassify legacy business rules into MIGRATE, DISCARD, or HUMAN DECISION outputs.
NUMU-IOReverse-engineer existing code into spec-kit migration artifacts with gap reporting.