Forge-Migration-Assessment

Provide a knowledge graph and analysis report of the current codebase plus the proposed target architecture. The Skill walks the graph to identify every affected node and edge, then produces an impact assessment with confidence labels and traceability.

The Skill scores migration complexity by surface area, blocker severity, and dependency depth, then recommends an ordering that resolves blockers like cyclic dependencies and god nodes before migrating dependent modules.

You need a knowledge graph with confidence-labelled edges, an analysis report, a dependency map, and optionally technical-debt findings, plus the proposed target architecture or migration scope. Graph freshness is verified before findings are treated as current.

Do not use it when no knowledge graph or analysis report exists, or when the change is a localized feature addition. For localized changes, use solution architecture design instead of full migration scoping.

No. It only interprets analysis outputs to produce impact assessments, risk registers, and sequencing recommendations. It does not approve migrations, commit to a target architecture, approve work items, or run the analysis tooling itself.