skills.rest
silaslopes100
silaslopes100COMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-curator

Analyze legacy system specifications to classify business rules for migration.

Updated May 19, 2026
Search Tags:#architecture#curation#migration#legacy#business-rules#reversa
One-click install
npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-curator-silaslopes100
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/silaslopes100/lojacarmenedaniel/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-curator-silaslopes100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex decision-making process during system migrations by evaluating legacy specifications against new architectural paradigms, ensuring that business rules are correctly migrated, discarded, or flagged for human intervention.

Core Features & Use Cases

  • Automated Rule Classification: Categorizes legacy business rules into MIGRAR, DESCARTAR, or DECISÃO HUMANA based on a predefined migration brief and paradigm decision.
  • Paradigm Alignment: Identifies legacy artifacts that are no longer necessary due to modern architectural shifts, such as moving from procedural locks to event-driven idempotency.
  • Traceability: Generates comprehensive logs (target_business_rules.md and discard_log.md) that provide full auditability for the migration team.

Quick Start

Execute the reversa-curator skill to analyze the legacy specifications in the _reversa_sdd directory and generate the migration decision artifacts.

Frequently Asked Questions about reversa-curator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine which legacy business rules to migrate or discard during a system migration?▼

To determine which legacy business rules to migrate or discard, analyze legacy specifications against new architectural paradigms to classify rules into migrate, discard, or human decision categories based on a predefined migration brief.

How does paradigm alignment identify legacy artifacts that are no longer necessary?▼

Paradigm alignment identifies unnecessary legacy artifacts by evaluating old specifications against new architectural shifts, such as moving from procedural locks to event-driven idempotency, and flagging obsolete business rules for automatic discarding.

What's the best way to maintain traceability when migrating business rules across an architectural paradigm shift?▼

The best way to maintain traceability when migrating business rules is to generate comprehensive target_business_rules.md and discard_log.md audit files, providing full visibility into migration decisions and discarded artifacts.

What inputs do I need to resolve ambiguities in legacy system migration specifications?▼

To resolve ambiguities in legacy system migration specifications, you need access to migration briefs, architectural paradigm decisions, and unit-level requirements to maintain consistency across the migration lifecycle.

Why does my legacy business rule migration produce inconsistencies between target rules and discarded artifacts?▼

Legacy business rule migration produces inconsistencies when the curation process lacks access to defined paradigm decisions and unit-level requirements, preventing accurate classification of ambiguities into migrate, discard, or human intervention categories.

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
sandecosandeco
1.5k

reversa-designer

Detect legacy topology and design migration-ready target specifications with traceability.

Community
Advanced
silaslopes100silaslopes100

reversa-designer

Design target system architectures and migration plans from legacy system analysis.

Community
Advanced
cliffthelincliffthelin

reversa-curator

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

Community
Advanced