skills.rest
AlexandrePontesjr
AlexandrePontesjrCOMMUNITY
Explore all skills by this author →
GitHub

reversa-curator

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

Updated May 5, 2026
Search Tags:#decision making#curation#migration#traceability#business rules#legacy specs#paradigm compatibility
One-click install
npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-curator-alexandrepontesjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-curator-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams migrate legacy rule sets by deciding, rule by rule, what to carry forward, what to discard, and what must be resolved by humans—based on legacy specs, the migration brief, and the target paradigm.

Core Features & Use Cases

  • Rule-by-rule migration decisions: categorizes each business rule as MIGRAR, DESCARTAR, or DECISÃO HUMANA using an explicit priority policy.
  • Human decision gating: sends ambiguous or missing-information items to DECISÃO HUMANA, with traceability and recommendations.
  • Migration artifacts generation: produces target_business_rules.md and discard_log.md, and maintains ambiguity tracking in ambiguity_log.md.
  • Paradigm-aware discard rationale: when discarding due to paradigm mechanisms changing, it records how the new paradigm absorbs the case.
  • Traceability to source: references the exact locations inside _reversa_sdd/ unit requirements/design files plus cross-input artifacts like migration_brief.md and paradigm_decision.md.

Quick Start

Ask the agent to run /reversa-curator to generate _reversa_sdd/migration/target_business_rules.md and _reversa_sdd/migration/discard_log.md from the existing _reversa_sdd migration inputs and unit specs.

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, discard, or send for human review?▼

Rule-by-rule migration decisions categorize each legacy business rule as MIGRAR, DESCARTAR, or DECISÃO HUMANA using an explicit priority policy. Decisions are driven by legacy specs, the migration brief, and the target paradigm to ensure traceable outcomes.

What is paradigm compatibility in legacy business rule migration?▼

Paradigm compatibility checks whether the target paradigm absorbs a legacy rule's mechanism. When discarding rules due to paradigm changes, the process records how the new paradigm natively handles the case to maintain a clear discard rationale.

How do I generate traceable migration artifacts for legacy business rules?▼

Migration artifacts are generated by processing unit specs and migration inputs to produce target_business_rules.md and discard_log.md. The process also updates ambiguity_log.md to maintain full traceability for items requiring human decisions.

How are ambiguous or missing-information legacy rules handled during migration?▼

Ambiguous legacy rules are gated to DECISÃO HUMANA with full traceability and recommendations. The process tracks these items in ambiguity_log.md, ensuring missing information is explicitly flagged for human resolution.

What inputs are required to start curating legacy business rules for migration?▼

Curating legacy business rules requires migration_brief.md, paradigm_decision.md, and per-unit requirements/design artifacts under the _reversa_sdd/ directory. These inputs provide the legacy specs and target paradigm context needed for rule-by-rule decisions.

When should I discard a legacy business rule during a system migration?▼

A legacy business rule should be discarded when the target paradigm absorbs its case or it no longer applies. The discard rationale is recorded in discard_log.md, explicitly noting how the new paradigm handles the scenario.

Related Skills

Explore More Software Engineering Skills→
RdindaRdinda
1

reversa-curator

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

Community
Advanced
simonheimlichersimonheimlicher
1

migrating-spec-to-spx

Guide legacy spec migrations to the SPX CODE framework with verification rules.

Community
Basic
Pabloprogramador23Pabloprogramador23

reversa-curator

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

Community
Advanced
cliffthelincliffthelin

reversa-curator

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

Community
Advanced