skills.rest
Markson22
Markson22COMMUNITY
Explore all skills by this author →
GitHub

reversa-curator

Classify legacy migration rules as migrate, discard, or human judgment.

Updated Nov 4, 2025
Search Tags:#templates#logs#migration#legacy#rule-engine#decisioning
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-curator-markson22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-curator-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assists teams in deciding, for each legacy migration rule, whether to migrate, discard, or escalate to human judgment, based on legacy specs and the migration brief.

Core Features & Use Cases

  • Rule-by-rule decisioning: classifies each legacy rule into MIGRAR, DESCARTAR, or DECISÃO HUMANA.
  • Outputs generation: produces target_business_rules.md and discard_log.md, and updates ambiguity_log.md as needed.
  • Use Case: Replace manual cross-checking of legacy rules with a structured, auditable decision workflow.

Quick Start

Invoke /reversa-curator to start evaluating legacy rules against the migration brief and paradigm decisions.

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 migration rules to keep or discard during a system migration?▼

Legacy migration rules are classified into migrate, discard, or human judgment categories by evaluating legacy specs against the migration brief and paradigm decisions, producing target_business_rules.md and discard_log.md.

What is the best way to automate legacy rule decisioning for a data migration project?▼

Automating legacy rule decisioning involves applying a rule-engine to evaluate each rule against a decision rubric, generating structured outputs like target_business_rules.md and discard_log.md for auditable migration workflows.

How does the rule classification process handle ambiguous legacy business rules?▼

Ambiguous legacy business rules are flagged for human judgment and logged into ambiguity_log.md, ensuring that uncertain rules are escalated rather than automatically migrated or discarded.

What input documents are needed to start evaluating legacy migration rules?▼

Evaluating legacy migration rules requires inputs from _reversa_sdd, migration_brief.md, and paradigm decision documents to accurately determine whether each rule should migrate or be discarded.

Can I manually cross-check legacy rules instead of using a structured decision workflow?▼

Manual cross-checking of legacy rules lacks the structured auditability of a decision workflow, which systematically classifies rules and generates discard_log.md to track what was discarded and why.

When should I escalate a legacy rule to human judgment during migration?▼

A legacy rule should be escalated to human judgment during migration when the decisioning process identifies ambiguity, referencing the decision rubric to safely flag it in ambiguity_log.md rather than forcing an automated choice.

Related Skills

Explore More Data & Analytics Skills→
cliffthelincliffthelin

reversa-paradigm-advisor

Classify legacy programming paradigms and map them to target stack paradigms.

Community
Advanced
RdindaRdinda
1

reversa-curator

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

Community
Advanced
vivekganavivekgana
4

data-classification

Automate schema- and content-based data classification and tagging across Unity Catalog.

Community
Advanced
ggazzoggazzo

reversa-curator

Analyze legacy specifications and migration briefs to generate target business rules and discard logs.

Community
Advanced