reversa-paradigm-advisor

Detect legacy paradigms from repository specs and generate paradigm_decision.md files.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-paradigm-advisor-stribus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-paradigm-advisor
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-paradigm-advisor
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-paradigm-advisor-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the legacy paradigm from specs and artifacts and generates a policy-backed paradigm_decision.md to align with the target stack, enabling informed migration decisions across teams.

Core Features & Use Cases

  • Detects the legacy paradigm from _reversa_sdd artifacts (e.g., migration_brief, domain_model, architecture) and produces a formal paradigm_decision.md.
  • Infers the natural target paradigm for the declared stack and enumerates viable alternatives with justifications.
  • Generates a structured paradigm_decision.md using the provided template, including evidences, uncertainties, and pending implications for downstream agents.
  • Activates via /reversa-paradigm-advisor to begin migration assessment during /reversa-migrate.

Quick Start

Activate the advisor with /reversa-migrate to generate paradigm_decision.md and start the migration assessment.

Frequently Asked Questions about reversa-paradigm-advisor

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

FAQPage Schema
How do I infer the legacy paradigm from repository specs for a migration assessment?

To infer the legacy paradigm, the advisor detects architectural patterns from repository specs and artifacts, then generates a formal paradigm_decision.md to align with the target stack for informed migration decisions.

How do I generate a paradigm decision document for a legacy architecture migration?

You can generate a paradigm_decision.md by activating the advisor during a migration assessment to populate the provided template with inferred target paradigms, viable alternatives, and formal justifications.

What is the best way to document architecture migration uncertainties and pending implications?

Documenting migration uncertainties requires generating a structured paradigm_decision.md that explicitly populates evidences, uncertainties, and pending implications for downstream agents to process.

Does this paradigm advisor work with existing domain_model and architecture artifacts?

Yes, the advisor detects the legacy paradigm by extracting evidence from existing artifacts like domain_model and architecture files to produce a policy-backed paradigm_decision.md.

Can I enumerate viable alternative target paradigms for a declared software stack?

Yes, the advisor infers the natural target paradigm for your declared stack and enumerates viable alternatives, providing evidence-backed justifications for each migration option.

When should I not use an automated paradigm inference tool for software migration?

Avoid using automated paradigm inference when repository specs or artifacts lack sufficient evidence, as the output relies on detecting existing architectural patterns to populate the formal decision document accurately.