skills.rest
lacsousa
lacsousaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-curator

Classifies legacy business rules into migrate, discard, or human-decision categories during system migration.

Updated Jun 12, 2026
Search Tags:#modernization#business rules#triage#paradigm shift#spec analysis#legacy migration#decision policy
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-curator-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-curator-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When migrating a legacy system, teams struggle to decide which business rules should carry over to the new system, which should be discarded, and which require human judgment. This Skill applies a deterministic decision policy to every rule found in legacy specs, producing auditable artifacts instead of ad-hoc choices. ## Core Features & Use Cases - Rule-by-rule triage: Inventories business rules from legacy requirements and design specs, then classifies each as MIGRAR, DESCARTAR, or DECISÃO HUMANA based on confidence level, migration brief scope, and paradigm compatibility. - Paradigm-aware discarding: Identifies rules that are artifacts of the legacy paradigm (e.g., pessimistic locks, 2PC transactions) and records how the target paradigm absorbs each case in a dedicated discard log. - Ambiguity escalation: Routes ambiguous or gap rules to a human-decision section with recommendations, and consolidates them into an ambiguity log. - Use Case: During a legacy-to-event-driven migration, run this agent after the paradigm decision is made to generate target_business_rules.md and discard_log.md with full traceability to source specs. ## Quick Start Ask the agent to run /reversa-curator after the migration brief and paradigm decision exist, so it can classify all legacy business rules and produce the migration artifacts.

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 to a new system?▼

Inventory each rule from legacy requirements and design specs, then apply an ordered decision policy: ambiguous or gap rules go to human decision, rules incompatible with the migration brief are discarded, paradigm-specific mechanisms are discarded with justification, and confirmed compatible rules migrate.

What artifacts does the reversa-curator agent produce?▼

It produces target_business_rules.md with MIGRAR, DESCARTAR, and DECISÃO HUMANA sections, a discard_log.md detailing every discarded rule, and updates to ambiguity_log.md. All artifacts are written to the _reversa_sdd/migration/ directory with source traceability.

When should a legacy rule be discarded due to paradigm change?▼

Discard a rule only when the new paradigm absorbs the use case by construction, such as replacing pessimistic locks with event-ID idempotency in event-driven systems. Pure business rules, regulatory rules, and domain invariants are never discarded for paradigm reasons.

What prerequisites are needed before running the migration curator?▼

The migration_brief.md and paradigm_decision.md files must exist in the _reversa_sdd/migration/ directory, meaning the Paradigm Advisor agent must have run first. If either is missing, the agent stops and instructs you to run the prior step.

How are ambiguous legacy rules handled during migration triage?▼

Ambiguous or gap rules always go to a dedicated DECISÃO HUMANA section with listed interpretations and a curator recommendation. They are also logged as PENDENTE in ambiguity_log.md and are never silently migrated or discarded.

Related Skills

Explore More Software Engineering Skills→
ggazzoggazzo

reversa-curator

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

Community
Advanced
MantisWareMantisWare

approve

Create and manage human-in-the-loop approval requests with lifecycle tracking.

Community
Advanced
RdindaRdinda
1

reversa-curator

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

Community
Advanced
b12consultingb12consulting
2

specs-setup

Initializes a spec-driven project structure with templates for requirements and governance.

Official
Intermediate