reversa-paradigm-advisor

To determine the target stack paradigm, you must analyze migration artifacts and specifications to detect the legacy paradigm, identify gaps, and produce a paradigm_decision.md document with evidence for downstream agents.

A paradigm_decision.md file records the rationale, evidence, and next steps for a migration paradigm choice, serving as a mandatory reference for all downstream agents to ensure alignment and conscious decision-making.

You analyze migration specifications by mapping the legacy programming paradigm to the inferred target stack paradigm, which flags compatibility gaps and alerts stakeholders to address missing architecture components.

Yes, the paradigm advisor works for software engineering migrations where specifications and domain documents exist, detecting legacy paradigms and guiding downstream Curator, Strategist, Designer, and Inspector agents.

A paradigm decision is required because it enforces conscious alignment across the migration workflow, ensuring downstream agents reference documented rationale and next steps rather than making assumptions about the target stack.

The limitation is that detection accuracy depends entirely on the completeness of migration specs and domain documents; missing artifacts prevent proper gap analysis and may result in incomplete paradigm_decision.md guidance.