Verified:GitHub

reversa-curator

Classify legacy business rules into MIGRATE, DISCARD, or HUMAN DECISION outputs.

Updated May 13, 2026

Search Tags:#migration #legacy governance #rule curation #audit traceability #policy decisioning #ambiguity handling #domain transformation

Ready to run

npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-curator-cliffthelin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reversa Curator turns messy legacy specifications into an audit-friendly migration plan by deciding, rule by rule, what to migrate, what to discard, and what must be escalated to humans.

Core Features & Use Cases

Migration decisioning: classifies each legacy business rule as MIGRATE, DISCARD, or HUMAN DECISION using the migration brief, chosen paradigm, and extracted legacy specifications.
Traceable outputs: produces target_business_rules.md plus discard_log.md and updates ambiguity_log.md for items requiring review.
Paradigm-aware governance: discards only legacy-paradigm mechanisms when the target paradigm absorbs the use case, while never silently discarding true business or regulatory rules.

Quick Start

Run reversa-curator to analyze _reversa_sdd migration artifacts and generate target_business_rules.md and discard_log.md for the migration team.

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 during a system transformation?▼

Legacy business rule migration decisions are made by classifying each rule as MIGRATE, DISCARD, or HUMAN DECISION using migration briefs and paradigm guidance, ensuring true regulatory policies are never silently discarded.

What is audit traceability in legacy rule migration and why is it needed?▼

Audit traceability in legacy rule migration tracks the rationale behind each MIGRATE, DISCARD, or HUMAN DECISION output, producing target_business_rules.md and discard_log.md to ensure compliance during domain transformation.

How do I handle ambiguity in legacy specifications when planning a migration?▼

Ambiguity handling in legacy migration involves flagging uncertain rules for HUMAN DECISION and logging them in ambiguity_log.md, preventing automated discard of potentially valid business logic during paradigm shifts.

What's the best way to safely discard legacy-paradigm mechanisms without losing business rules?▼

Safely discarding legacy-paradigm mechanisms requires paradigm-aware governance that only discards obsolete technical mechanisms when the target paradigm absorbs the use case, while escalating true business rules to human review.

How do I generate a rule-by-rule migration plan from multiple legacy unit rule sets?▼

Generating a rule-by-rule migration plan from multiple legacy unit rule sets involves inventorying rules with confidence signals, applying a curator decision policy, and rendering structured markdown logs for the migration team.

Do I need specific input artifacts to start the legacy rule curation process?▼

Yes, the legacy rule curation process requires reading _reversa_sdd migration inputs, including migration briefs and extracted legacy specifications, to produce accurate target business rule and discard logs.