reversa-curator

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

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-curator-afsjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-curator-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The reversa-curator skill prevents incorrect migrations by deciding—rule by rule—what to migrate, what to discard, and what requires human review, using the legacy specs, the migration brief, and the chosen decision paradigm.

Core Features & Use Cases

  • Rule triage for migration: Classifies each legacy business rule into MIGRAR, DESCARTAR, or DECISÃO HUMANA with explicit rationale and traceability.
  • Outputs migration artifacts: Produces _reversa_sdd/migration/target_business_rules.md and _reversa_sdd/migration/discard_log.md, and updates _reversa_sdd/migration/ambiguity_log.md.
  • Paradigm-aware safety: Detects rules that are merely legacy mechanism artifacts (e.g., transaction/locking patterns) and discards them only when the new paradigm absorbs the use case by design.

Quick Start

Run the Curator via the activation command /reversa-curator, ensuring the files _reversa_sdd/migration/migration_brief.md and _reversa_sdd/migration/paradigm_decision.md are present.

Frequently Asked Questions about reversa-curator

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

FAQPage Schema
How do I triage legacy business rules for migration into migrate, discard, or human review categories?

Rule triage for migration classifies each legacy business rule into MIGRAR, DESCARTAR, or DECISÃO HUMANA with explicit rationale and traceability. It analyzes legacy specifications against the migration brief and selected decision paradigm to determine rule-by-rule migration outcomes.

What artifacts are produced when categorizing business rules for a migration plan?

Categorizing business rules for migration produces target_business_rules.md, discard_log.md, and updates ambiguity_log.md. These traceable artifacts are generated in the _reversa_sdd/migration/ directory for downstream agents to consume during the migration process.

When should I discard legacy business rules during a system migration?

Discard legacy business rules during system migration when they are merely legacy mechanism artifacts, such as transaction or locking patterns, and the new paradigm absorbs the use case by design. This paradigm-aware safety detects and removes obsolete rules.

Do I need a migration brief and paradigm decision before starting rule triage?

You need a migration brief and paradigm decision before starting rule triage. Ensure the files migration_brief.md and paradigm_decision.md are present in the _reversa_sdd/migration/ directory, as the tool reads legacy specs from _reversa_sdd/ and evaluates them against these inputs.

How does human-in-the-loop decision making work for ambiguous legacy rules?

Human-in-the-loop decision making for ambiguous legacy rules flags them as DECISÃO HUMANA and logs them in ambiguity_log.md. This ensures rules that cannot be automatically categorized for migration or discard are explicitly traced for manual resolution.