reversa-curator

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

Updated May 8, 2025
One-click install
npx skills add https://github.com/ggazzo/brewpilot --skill reversa-curator-ggazzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-curator
Source: https://github.com/ggazzo/brewpilot/tree/main/.agents/skills/reversa-curator
Command: npx skills add https://github.com/ggazzo/brewpilot --skill reversa-curator-ggazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires _reversa_sdd/migration/migration_brief.md, _reversa_sdd/migration/paradigm_decision.md, _reversa_sdd/<unit>/requirements.md, _reversa_sdd/<unit>/design.md, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the decision-making process for migrations, ensuring that only relevant data and rules are transferred to the new system, reducing manual effort and potential errors.

Core Features & Use Cases

  • Decision Automation: Automatically decides what data migrates, what is discarded, and what requires human intervention based on legacy specifications, migration briefs, and paradigms.
  • Target Business Rules Generation: Produces target_business_rules.md with detailed decisions for each rule.
  • Discard Log Creation: Generates discard_log.md with explanations for discarded items.
  • Ambiguity Log Update: Updates _reversa_sdd/migration/ambiguity_log.md with pending decisions.
  • Use Case: Ideal for organizations undergoing large-scale migrations where manual decision-making is time-consuming and prone to errors.

Quick Start

Activate the reversa-curator skill with the command: /reversa-curator

Frequently Asked Questions about reversa-curator

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

FAQPage Schema
How do I automate software migration decisions for large-scale system transitions?

Automate software migration decisions by analyzing legacy specifications, migration briefs, and paradigm decisions to generate target business rules and discard logs. This reduces manual effort and errors by systematically determining what data migrates, what is discarded, and what needs human intervention.

What is code migration decision automation and when do I need it?

Code migration decision automation is the process of using tools to evaluate legacy specifications against migration paradigms to determine data transfer rules. You need it during large-scale migrations where manual decision-making is time-consuming and prone to human error.

How do I track discarded data and ambiguous rules during a code migration?

Track discarded data and ambiguous rules during code migration by generating a discard log with explanations for discarded items and updating an ambiguity log with pending decisions. This ensures full traceability for items not transferred to the new system.

Do I need legacy specifications and migration briefs to automate migration decisions?

Yes, you need legacy specifications, migration briefs, and paradigm decision documents to automate migration decisions. These inputs are required to accurately determine what data and rules transfer to the new system versus what requires human intervention.

What's the best way to generate target business rules during a software migration?

Generate target business rules during software migration by analyzing legacy specifications and paradigm decisions automatically. This approach produces detailed decision documents for each rule, ensuring only relevant data and logic are transferred to the new system.