reversa-paradigm-advisor

Identify system paradigms from specifications and document migration decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Reversa Paradigm Advisor Skill identifies the programming paradigm of a legacy system, infers the natural paradigm of the target stack, alerts on paradigm gaps, and facilitates informed user decisions, ensuring a successful migration process.

Core Features & Use Cases

  • Paradigm Detection: Determines the paradigm of a legacy system from specs and the natural paradigm of the target stack.
  • Gap Analysis: Identifies and describes gaps between the legacy and target paradigms with examples from the system.
  • Decision Facilitation: Presents three options for bridging paradigm gaps and collects the user's decision and rationale.
  • Documentation: Outputs a comprehensive decision document outlining the identified paradigm, gaps, options, and user choices for further use.

Quick Start

Execute the 'reversa-paradigm-advisor' command to start the process.

Frequently Asked Questions about reversa-paradigm-advisor

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

FAQPage Schema
How do I identify programming paradigm gaps during a system migration?

To identify paradigm gaps during system migration, analyze legacy specifications to detect the current programming paradigm and infer the target stack's natural paradigm. This paradigm analysis highlights structural mismatches with concrete examples, enabling informed software migration decisions.

What is the best way to document software migration decisions for paradigm shifts?

The best way to document software migration decisions is to generate a comprehensive decision document outlining the identified paradigms, detected gaps, available bridging options, and the user's selected rationale, ensuring technical teams maintain clear migration workflows.

How do I bridge paradigm mismatches when migrating legacy code to a new tech stack?

Bridging paradigm mismatches involves evaluating three distinct options for aligning the legacy system with the target stack paradigm. You must facilitate decision-making by selecting a specific bridging approach and documenting its rationale for the migration workflow.

Do I need full system specifications to analyze a legacy programming paradigm?

Yes, you need in-depth system specifications and target stack knowledge to accurately perform paradigm analysis. Without comprehensive legacy specifications, detecting paradigm gaps and generating reliable software migration decision documentation is not possible.

Can I automate decision-making for code migration workflows with paradigm analysis?

You cannot fully automate decision-making for code migration workflows because user input is required. Paradigm analysis can detect gaps and present options, but technical teams must actively facilitate informed software decisions by choosing a specific migration strategy.

Why does code migration fail when the target stack uses a different programming paradigm?

Code migration fails due to unaddressed paradigm gaps between the legacy system and the target stack. Identifying these structural mismatches early through paradigm analysis and facilitating informed bridging decisions prevents software migration failures.