reversa-curator

Classify legacy business rules as migrate, discard, or human decision for Reversa migrations.

1|Updated Dec 20, 2025

Search Tags:#migration #agent workflow #decision #traceability #business rules #paradigm mapping #legacy specs

Ready to run

npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-curator-rdinda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-curator-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents migration failures and scope drift by systematically deciding, rule by rule, what legacy business rules should migrate, what should be discarded, and what requires human judgment.

Core Features & Use Cases

Rule-by-rule migration decisions: Classifies each identified legacy rule as MIGRAR, DESCARTAR, or DECISÃO HUMANA based on the migration brief and chosen paradigm.
Ambiguity and gaps handling: Sends ambiguous or missing-rule cases to human decision and records them in an ambiguity log with cross-references.
Migration artifact generation: Produces target_business_rules.md and a structured discard_log.md with explicit justifications and provenance.

Quick Start

Run /reversa-curator after /reversa-migrate so it reads the legacy specs and brief, then generates the migration decision artifacts in _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 which legacy business rules to migrate or discard?▼

To decide which legacy business rules to migrate or discard, classify each rule as MIGRATE, DISCARD, or HUMAN DECISION based on your migration brief and chosen paradigm. This systematic rule-by-rule evaluation prevents migration failures and scope drift while generating target_business_rules.md and discard_log.md artifacts.

What is the best way to handle ambiguous business rules during a migration?▼

Handling ambiguous business rules during migration requires routing them to human decision and logging them in an ambiguity log with cross-references. This ensures missing-rule cases receive explicit review rather than being silently dropped or incorrectly migrated from legacy unit specs.

How do I generate traceability logs for discarded business rules?▼

Generating traceability logs for discarded business rules requires rendering a structured discard_log.md with explicit justifications and provenance for each rule. This artifact documents why specific legacy rules were excluded from the target paradigm mapping during the agent workflow.

What files do I need before running a rule inventory migration decision?▼

Running a rule inventory migration decision requires migration_brief.md, paradigm_decision.md, and domain or code-analysis artifacts to be present. These input files provide the migration scope and paradigm context needed to evaluate legacy unit specs and classify rules.

When do I need to run the migration curator in an agent workflow?▼

You need to run the migration curator after the initial migration step so it can read legacy specs and the brief, then generate decision artifacts. It confines outputs to the _reversa_sdd/migration/ directory and updates ambiguity_log.md with pending items requiring human review.