reversa-strategist

Evaluates legacy migration strategies and produces risk registers and cutover plans.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/RLuf/fzagent --skill reversa-strategist-rluf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-strategist
Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-strategist
Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-strategist-rluf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing how to migrate a legacy system is a high-stakes decision with unclear trade-offs. This Skill structures that decision by evaluating applicable migration strategies against your project brief, paradigm gap, and risk appetite, then producing a justified recommendation, a risk register, and a cutover plan while leaving the final choice to a human. ## Core Features & Use Cases - Strategy evaluation with explicit trade-offs: Filters strategies from a catalog (Strangler Fig, Big Bang, Parallel Run, Branch by Abstraction) and scores each against appetite, paradigm gap, cost, risk, and time. - Risk register generation: Produces risk_register.md covering technical, operational, organizational, regulatory, and data risks, each with probability, impact, mitigation, contingency, and owner. - Cutover planning: Generates cutover_plan.md with prerequisites, window, step-by-step owners and durations, rollback plan, and go/no-go criteria. - Use Case: After the Curator has documented target business rules for a legacy banking system, invoke this Skill to compare Strangler Fig versus Parallel Run, receive a justified recommendation, and get a complete risk register and cutover plan ready for human sign-off. ## Quick Start Run /reversa-strategist after the migration brief, paradigm decision, and target business rules exist to generate the strategy, risk register, and cutover plan in _reversa_sdd/migration/.

Frequently Asked Questions about reversa-strategist

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

FAQPage Schema
How do I choose a legacy system migration strategy?▼

Filter applicable strategies from the catalog based on your brief, then score each against risk appetite, paradigm gap, cost, risk, and time. The Skill recommends one strategy with traceable justification, but the final decision remains human.

What migration strategies does the reversa framework support?▼

The catalog covers Strangler Fig, Big Bang, Parallel Run, and Branch by Abstraction. Each entry documents when it applies, its cost, risk, and duration profile, and which risk appetite it favors.

When should I use Parallel Run instead of Big Bang migration?▼

Use Parallel Run when the system has critical financial, fiscal, or regulatory logic requiring proof of equivalence over time. Big Bang is only acceptable for small systems with few live integrations and a transformational appetite.

What inputs does the migration strategist need before running?▼

It requires migration_brief.md, paradigm_decision.md, and target_business_rules.md from a completed Curator phase, plus domain, architecture, dependencies, and inventory documents for context.

Can Big Bang migration be used for regulated systems?▼

No. Systems with regulatory integrations must never use Big Bang. The Skill always includes Parallel Run as an alternative for regulated domains to validate parity of critical rules.