reversa-strategist

Select migration strategies and generate planning documents from system briefs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the selection of migration strategies for system migration, considering trade-offs and producing comprehensive planning documents.

Core Features & Use Cases

  • Strategy Selection: Evaluates migration strategies and recommends one based on the provided brief, paradigms, and appetite.
  • Comprehensive Planning: Generates migration_strategy.md, risk_register.md, and cutover_plan.md for detailed planning.
  • Use Case: Imagine you are migrating a legacy system. This Skill can automatically produce a migration plan and risk register based on your inputs, saving time and reducing errors.

Quick Start

/reversa-strategist to produce a migration strategy based on the current migration context.

Frequently Asked Questions about reversa-strategist

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

FAQPage Schema
How do I automate migration strategy selection for a legacy system?

To choose a migration strategy, evaluate system brief, architecture, dependencies, and inventory against your risk appetite. Strategies like Strangler Fig, Big Bang, Parallel Run, and Branch by Abstraction offer different trade-offs in cutover risk, downtime, and complexity, which this tool automates evaluating for you.

What is the best way to generate a cutover plan and risk register for system migration?

Generate a cutover plan and risk register by providing context, domain, architecture, dependencies, and inventory input artifacts. The automation produces markdown documents including migration_strategy.md, risk_register.md, and cutover_plan.md to manage explicit strategy and risk cutover.

When should I use Strangler Fig versus Big Bang migration strategy?

Use Strangler Fig for incremental migration with lower risk, or Big Bang for complete, rapid cutover with higher risk. The tool selects between these and strategies like Parallel Run and Branch by Abstraction by evaluating your system brief, paradigms, and appetite to match your specific trade-off tolerance.

What input artifacts do I need to produce a migration strategy automatically?

To produce a migration strategy automatically, you need input artifacts detailing your system context, domain, architecture, dependencies, and inventory. These inputs allow the tool to evaluate trade-offs and recommend an appropriate strategy with comprehensive planning documents.

Does automated migration planning work without explicit dependency and inventory documentation?

Automated migration planning requires explicit input artifacts for context, domain, architecture, dependencies, and inventory. Without these inputs, the tool cannot accurately evaluate migration strategies, trade-offs, or generate comprehensive risk and cutover planning documents.