reversa-curator

Classify migration rules from legacy specifications into migrate, discard, or human review.

Updated Jun 6, 2026

Search Tags:#automation #migration #legacy #decision-making #curator #rule-analysis

Ready to run

npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-curator-pabloprogramador23

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Curator decides, rule by rule, what migrates to the new system, what is discarded, and what requires human review, based on legacy specs, the migration brief, and paradigm decisions.

Core Features & Use Cases

Filters legacy rules against migration_brief.md and paradigm_decision.md to determine migration viability.
Produces two artifacts: target_business_rules.md and discard_log.md, with explicit traceability to the legacy sources.
Orchestrates human-in-the-loop decisions when ambiguity or gaps are detected, ensuring safe and auditable migrations.

Quick Start

Run the curator on the current inputs to generate target_business_rules.md and discard_log.md for review.

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, you filter legacy specifications against a migration brief and paradigm decisions, producing a structured plan that designates rules for migration, discarding, or human review.

What is the best way to maintain traceability when migrating legacy specifications?▼

Maintaining traceability when migrating legacy specifications requires producing target business rules and discard logs with explicit references to legacy sources, ensuring auditable governance across all migration units.

How do I handle ambiguous rules during a legacy system migration?▼

Handling ambiguous rules during legacy system migration involves orchestrating human-in-the-loop decisions when gaps are detected, ensuring safe and auditable migrations by flagging items for explicit human review.

What inputs do I need to classify migration rules from legacy systems?▼

Classifying migration rules from legacy systems requires three inputs: a migration brief, a paradigm decision document, and per-unit design and requirements documents to determine migration viability.