reversa-paradigm-advisor

Detect legacy programming paradigms from migration specs and write paradigm_decision.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents users from treating a migration as a mere syntax change by explicitly detecting the legacy programming paradigm, inferring the natural target paradigm, and forcing a conscious decision about how to handle paradigm gaps.

Core Features & Use Cases

  • Legacy paradigm detection from specs: classifies the legacy’s likely paradigm using evidence from _reversa_sdd/ artifacts (not source code), with confidence tagging (🟢/🟡/🔴/⚠️).
  • Target paradigm inference from the migration brief: maps the declared target stack in migration_brief.md to the natural paradigm and documents alternatives.
  • Concrete gap articulation + decision gate: presents a non-abstract, evidence-based list of implications and always asks for one of three migration options, then writes the mandatory _reversa_sdd/migration/paradigm_decision.md artifact for subsequent agents.

Quick Start

Run /reversa-migrate to ensure the migration brief is created, then activate /reversa-paradigm-advisor to generate _reversa_sdd/migration/paradigm_decision.md based on the detected legacy paradigm and inferred target natural paradigm.

Frequently Asked Questions about reversa-paradigm-advisor

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

FAQPage Schema
How do I detect legacy programming paradigms before a code migration?

Legacy programming paradigm detection involves analyzing migration discovery specifications and artifacts to classify the existing paradigm using tagged evidence, preventing mental-model mismatches when moving to a new target stack.

What happens if legacy paradigm detection is ambiguous during migration?

When legacy paradigm detection is ambiguous during migration, the process supports optional extra reads of discovery artifacts to gather more evidence, ensuring the final paradigm classification is accurate before proceeding.

How do I document paradigm gaps for a target stack migration?

You document paradigm gaps by comparing the detected legacy paradigm with the target stack's natural paradigm, articulating concrete implications, and capturing user-consent decisions in a formal decision markdown artifact.

Do I need source code to analyze legacy paradigm behavior for migration?

No, you do not need source code to analyze legacy paradigm behavior. The classification relies entirely on evidence extracted from migration discovery specifications and artifacts, not the actual source codebase.

Why should I choose a migration paradigm before changing syntax?

Choosing a migration paradigm before changing syntax prevents treating a migration as a mere syntax change, forcing a conscious decision about how to handle structural and mental-model gaps between legacy and target systems.

Can I infer the target paradigm directly from a migration brief?

Yes, you can infer the target paradigm directly from a migration brief by mapping the declared target stack details to its natural programming paradigm and documenting available alternatives for the workflow.