reversa-strategist

Name: reversa-strategist
Availability: InStock
Author: Ricardo

Analyze migration briefs and constraints to recommend a migration strategy with risk and cutover artifacts.

Updated May 16, 2026

Search Tags:#legacy modernization #paradigm shift #risk register #migration strategy #cutover planning #regulatory constraints

Ready to run

npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-strategist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-strategist
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-strategist
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-strategist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps migration teams decide the best migration strategy by turning the migration brief, target paradigm, and appetite into a justified recommendation plus actionable plans.

Core Features & Use Cases

Strategy evaluation with trade-offs: Compares multiple applicable migration strategies and makes the recommendation depend on brief constraints, paradigm gap, and risk appetite.
Migration deliverables: Produces a migration strategy document, a risk register, and a cutover plan for the recommended approach.
Regulatory-aware safety: Ensures strategy guidance accounts for critical business rules and explicitly registers operational risks when paradigm change is large.

Quick Start

Trigger reversa-strategist for the migration brief and paradigm decision artifacts so it generates migration_strategy.md, risk_register.md, and cutover_plan.md in _reversa_sdd/migration/.

Frequently Asked Questions about reversa-strategist

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

FAQPage Schema

What is the best way to choose a legacy modernization migration strategy?▼

Choosing a legacy modernization migration strategy requires evaluating trade-offs among Strangler Fig, Big Bang, Parallel Run, and Branch by Abstraction. The optimal path depends on your migration brief constraints, paradigm gap, and risk appetite.

How do I plan a cutover for a legacy system rebuild?▼

Planning a cutover for a legacy system rebuild involves generating a cutover_plan.md derived from your migration context. This plan is produced alongside a migration strategy document and a risk register with explicit risk ownership.

When do I need a risk register for a paradigm shift migration?▼

You need a risk register for a paradigm shift migration when the change is large and involves regulatory constraints. It explicitly registers operational risks and assigns risk ownership based on business-rule constraints.

How does Strangler Fig compare to Big Bang for legacy migration?▼

Strangler Fig compares to Big Bang by offering incremental migration versus a single event transition. Evaluating them requires analyzing your migration brief and target paradigm decision to justify the recommended approach with explicit trade-offs.

Can I use Parallel Run for legacy modernization with regulatory constraints?▼

Parallel Run is applicable for legacy modernization with regulatory constraints when you need both old and new systems operating simultaneously. Selection depends on analyzing business-rule constraints and your target paradigm decision.

What artifacts do I need to start migration strategy evaluation?▼

To start migration strategy evaluation, you need the migration brief and target paradigm decision artifacts. These inputs enable analysis of business-rule constraints to generate migration_strategy.md, risk_register.md, and cutover_plan.md.