skills.rest
stribus
stribusCOMMUNITY
Explore all skills by this author →
GitHub

reversa-curator

Categorize legacy migration rules as MIGRAR, DESCARTAR, or DECISÃO HUMANA.

1|Updated Nov 20, 2025
Search Tags:#migration#legacy#decision-log#auditable#paradigm-shift#rule-curation
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-curator-stribus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-curator-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This component automates the evaluation and routing of legacy migration rules to a modern system, deciding which rules migrate, which should be discarded, and which require human review.

Core Features & Use Cases

  • Decision orchestration: evaluates inputs from _reversa_sdd and outputs target_business_rules.md and discard_log.md.
  • Auditable governance: maintains clear traceability of decisions according to migration_brief.md and paradigm_decision.md.
  • Artifact generation: produces migration artifacts ready for downstream writers.

Quick Start

Run the /reversa-curator workflow to generate target_business_rules.md and discard_log.md from the current _reversa_sdd inputs.

Frequently Asked Questions about reversa-curator

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

FAQPage Schema
How do I automate legacy rule migration decisions for a new system?▼

Legacy rule migration decisions are automated by evaluating inputs against a migration brief and paradigm decisions, categorizing each rule to migrate, discard, or flag for human review. This produces auditable target business rules and discard logs ready for downstream use.

What is the best way to maintain an auditable decision log during a paradigm shift migration?▼

An auditable decision log is maintained by routing every legacy rule through a decision rubric that compares items against paradigm decisions, ensuring clear traceability for all migrated, discarded, or manually reviewed rules.

How do I generate target business rules and discard logs from existing legacy documentation?▼

Target business rules and discard logs are generated by running the curator workflow against current legacy documentation inputs, applying a decision rubric to automatically output ready-to-use migration artifacts.

When do I need human review for legacy migration rules?▼

Human review for legacy migration rules is needed when the evaluation rubric cannot confidently categorize an item as migrate or discard, routing it to a manual decision category to ensure safe outcomes.

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

Categorizing legacy rules requires providing the specific legacy documentation inputs described in the system directory, along with a migration brief and paradigm decisions to evaluate and route each item accurately.

Can I use this rule curation approach without a predefined migration brief?▼

Rule curation without a predefined migration brief is not supported, as the evaluation rubric requires a migration brief and paradigm decisions to ensure auditable outcomes for each legacy rule.

Related Skills

Explore More Software Engineering Skills→
Marcu-LoretoMarcu-Loreto

reversa-paradigm-advisor

Detect paradigm mismatches and generate a decision document for system migration.

Community
Advanced
afsjrafsjr

reversa-curator

Classify legacy business rules into migrate, discard, or human decision categories.

Community
Advanced
tcfialhotcfialho

nexus2-spec

Draft and update product specification documents with structured sections and business rules.

Community
Basic
ggazzoggazzo

reversa-curator

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

Community
Advanced