reversa-strategist

Synthesize migration brief constraints to generate migration_strategy, risk_register, and cutover_plan artifacts.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-strategist-afsjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-strategist
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-strategist
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-strategist-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Este Skill ajuda a selecionar e justificar uma estratégia de migração, deixando trade-offs explícitos e preparando um plano prático de cutover com um registro de riscos acionável.

Core Features & Use Cases

  • Avaliação orientada por contexto: sintetiza brief, decisão de paradigma, apetite e restrições do projeto para estimar impacto e viabilidade.
  • Seleção de estratégias com catálogo: consulta references/migration-strategies.md, filtra alternativas aplicáveis e compara custo, risco e tempo.
  • Recomendação com rastreabilidade: marca uma estratégia como recomendada (ou indica sinais de alerta) com justificativa baseada nos artefatos de entrada.
  • Saídas operacionais: produz migration_strategy.md, risk_register.md e cutover_plan.md para orientar a escolha humana e a execução.
  • Gestão de riscos por mudança de paradigma e dados: adiciona riscos de paradigma, operacionais, regulatórios e de dados com owner, mitigação e contingência.

Quick Start

Ative o agente via /reversa-strategist para gerar migration_strategy.md, risk_register.md e cutover_plan.md a partir do brief, paradigma e apetite do projeto.

Frequently Asked Questions about reversa-strategist

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

FAQPage Schema
How do I choose between Strangler Fig and Big Bang for a production migration strategy?

A cutover plan guides the transition to a new system during migration. You generate it by evaluating migration brief constraints and paradigm shifts, producing an actionable cutover_plan.md that aligns with the selected migration strategy and derived risk appetite.

How do I build a risk register for a system migration involving a paradigm shift?

Building a risk register for a paradigm shift migration involves identifying operational, regulatory, and data risks. You generate a risk_register.md by mapping mitigation and contingency actions with assigned owners based on the derived project appetite and target paradigm implications.

When should I use Branch by Abstraction versus Parallel Run for software migration?

You should use Branch by Abstraction or Parallel Run based on your project constraints and risk appetite. By consulting a local migration strategy catalog, you filter applicable patterns, comparing cost, risk, and execution time to recommend the optimal strategy with clear trade-offs.

What is needed to generate a migration strategy and cutover plan for a production system?

To generate a migration strategy and cutover plan, you need a migration brief, target paradigm decision, and derived risk appetite. These inputs are synthesized under migration SDD constraints to produce operational artifacts for human decision control and execution guidance.