reversa-strategist

Generate migration strategy, risk register, and cutover plan artifacts.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-strategist-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-strategist
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-strategist
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-strategist-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps migration teams choose and justify an actionable migration strategy by evaluating trade-offs, aligning with the migration brief and target paradigm, and preparing a concrete cutover and risk register.

Core Features & Use Cases

  • Strategy evaluation & recommendation: Compares multiple migration approaches and recommends one while making trade-offs explicit for human decision-making.
  • Risk register generation: Produces a structured risk register covering strategy risks, paradigm-change implications, data risks, operational risks, and organizational risks with identifiable owners.
  • Cutover plan creation: Generates an operational cutover plan (and rollback criteria) tailored to the recommended strategy and guided by go/no-go conditions.
  • Migration artifacts workflow: Writes outputs exclusively under _reversa_sdd/migration/ to keep deliverables consistent and controlled.

Quick Start

Use the reversa-strategist skill to generate a migration strategy, risk register, and cutover plan from your migration brief and paradigm decision.

Frequently Asked Questions about reversa-strategist

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

FAQPage Schema
How do I choose the best migration strategy for a legacy system?

A cutover plan coordinates the transition from a legacy system to a target architecture using go/no-go conditions and rollback criteria. It ensures operational readiness by detailing safe transition steps and fallback options tailored to the recommended migration strategy.

What is a Strangler Fig migration pattern and when should I use it?

A risk register for system migration identifies strategy, data, operational, and organizational risks with assignable owners. It structures risk management by capturing paradigm-change implications and operational readiness vulnerabilities before executing the cutover plan.

How do I create a cutover plan with rollback criteria for a system migration?

A Big Bang migration strategy transfers the entire legacy system to the target architecture in a single transition event. It requires strict operational readiness and comprehensive risk management due to high cutover risk, unlike incremental approaches like Strangler Fig or Parallel Run.

Do I need a legacy inventory and architecture dependencies before planning a migration strategy?

Parallel Run migration executes both legacy and target systems simultaneously to validate operational readiness before full cutover. This strategy reduces data risk and operational risk by comparing outputs, unlike Big Bang migration which transitions all services immediately without a validation period.

What migration artifacts do I need to manage operational readiness during a paradigm shift?

Branch by Abstraction is a migration strategy that introduces an abstraction layer to decouple legacy system components before replacement. This pattern supports incremental migration and operational readiness by allowing parallel development while minimizing disruption to the target architecture.