What problem does it solve? Migrating a legacy system requires deciding, rule by rule, what carries over to the new system, what gets discarded, and what needs a human decision. Doing this ad hoc loses traceability and lets ambiguous or missing rules slip through silently. This Skill applies a deterministic decision policy over legacy specs to produce auditable migration artifacts. ## Core Features & Use Cases - Rule-by-rule decision policy: Classifies each legacy business rule as MIGRAR, DESCARTAR, or DECISÃO HUMANA based on confidence level (🟢/🟡/🔴/⚠️), the migration brief, and the chosen target paradigm. - Paradigm-aware discarding: Identifies rules that are artifacts of the legacy paradigm (e.g., pessimistic locks, 2PC, Active Record) and records how the new paradigm absorbs each case, with a dedicated discard log. - Traceable artifacts: Generates target_business_rules.md, discard_log.md, and updates ambiguity_log.md inside _reversa_sdd/migration/, with explicit source references for every decision. - Use Case: After running the reversa discovery and paradigm-advisor agents on a legacy codebase, invoke this Skill to triage all extracted business rules before the Strategist plans the migration, ensuring ambiguous rules always reach a human. ## Quick Start Run /reversa-curator after the migration brief and paradigm decision exist to classify all legacy business rules into migrate, discard, and human-decision lists.
