reversa-curator

Decides which legacy business rules migrate, discard, or need human review during system migration.

Updated May 22, 2026
One-click install
npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-curator-gleisonoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/GleisonOliveira/dockerpilot-mcp/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-curator-gleisonoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When migrating a legacy system, teams must decide rule by rule what carries over to the new system, what gets discarded, and what requires human judgment. This Skill automates that triage by applying an explicit decision policy against legacy specs, the migration brief, and the chosen target paradigm. ## Core Features & Use Cases - Rule-by-rule triage: Inventories business rules from legacy specs and classifies each as MIGRATE, DISCARD, or HUMAN DECISION with full traceability to source artifacts. - 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. - Structured outputs: Produces target_business_rules.md, discard_log.md, and updates ambiguity_log.md using bundled templates. - Use Case: After running the discovery and paradigm-advisor agents on a legacy codebase, invoke this Skill to generate a curated catalog of business rules with migration decisions before handing off to the Strategist agent. ## Quick Start Ask the agent to run the Curator step of the migration workflow to classify all legacy business rules into migrate, discard, and human-decision lists.

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 the legacy 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 when the paradigm changes, and confirmed compatible rules migrate.

What artifacts does the reversa-curator skill produce?▼

It produces target_business_rules.md with migrate, discard, and human-decision sections, a detailed discard_log.md with paradigm-linked items, and updates ambiguity_log.md with pending items. All outputs are written to the migration folder with source traceability.

What inputs are required before running the migration curation step?▼

It requires migration_brief.md and paradigm_decision.md in the migration folder, plus requirements.md and design.md per unit from the discovery phase. Auxiliary files like domain.md, gaps.md, and pain points improve decision quality.

When should a legacy rule be discarded versus migrated during a paradigm shift?▼

Discard a rule only when the new paradigm absorbs the case by construction, such as replacing pessimistic locks with event idempotency. Pure business rules, regulatory rules, and domain invariants are never discarded; they only change location in the new paradigm.

What happens to ambiguous or incomplete legacy rules?▼

Ambiguous rules and gaps always go to human decision, never silently to migrate or discard. Each item gets listed with interpretation options, a curator recommendation, and a pending status tracked in the ambiguity log.