reversa-strategist

Evaluate migration strategies and generate strategy, risk, and cutover plan artifacts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/maximoseo/github-repos-radar --skill reversa-strategist-maximoseo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-strategist
Source: https://github.com/maximoseo/github-repos-radar/tree/main/.agents/skills/reversa-strategist
Command: npx skills add https://github.com/maximoseo/github-repos-radar --skill reversa-strategist-maximoseo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates migration planning for complex systems by comparing multiple strategies, articulating trade-offs, and producing governance-ready artifacts to inform human decisions.

Core Features & Use Cases

  • Evaluates multiple migration strategies (Strangler Fig, Big Bang, Parallel Run, Branch by Abstraction) with explicit trade-offs.
  • Generates artifact outputs (migration_strategy.md, risk_register.md, cutover_plan.md) aligned to the chosen path.
  • Provides a defensible rationale based on the brief, paradigm decisions, and organizational appetite to accelerate governance and execution.

Quick Start

Describe your migration brief, appetite, and constraints, and I will generate strategy options and implementation artifacts.

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 plan a complex system migration with paradigm gaps?▼

System migration planning compares multiple strategies like Strangler Fig or Parallel Run to articulate trade-offs and produce governance-ready artifacts for human decision-making.

How do I decide between Strangler Fig and Big Bang migration strategies?▼

Comparing migration strategies involves evaluating organizational appetite for change and paradigm gaps to generate at least two viable options with explicit trade-offs and risk registers.

How do I create a cutover plan and risk register for a system transition?▼

Creating a cutover plan involves outlining ownership and transition steps based on your chosen migration path, generating artifacts like cutover_plan.md and risk_register.md for governance.

When should I use Branch by Abstraction for a software migration?▼

Branch by Abstraction suits migrations where you need to vary your appetite for change, allowing incremental system transitions while satisfying technical and organizational constraints.

Can I use parallel run strategy for complex system transitions with high risk?▼

Parallel run is a viable migration strategy for complex system transitions, generating a defensible rationale and risk register to satisfy technical and organizational constraints under high risk.