| name | migration-advisor |
| description | Front door for legacy migrations — assess a legacy system from shallow read-only signals (repo probe, git history, a reachable running instance) plus a short interview, then recommend an entry path (rehost, replatform, rearchitect) and an ordered sequence of migration skills to invoke. Produces migration/PLAN.md with its evidence shown; routes, never executes. Use when someone wants to migrate, modernize, or port a legacy enterprise Java or web application and needs to know where to start. Triggers on "migrate this legacy app", "how do I modernize this", "port this old system", "where do I start with this legacy codebase", "plan a migration". |
Migration Advisor
The triage front door. Legacy migration is judgment-heavy and the entry-path choice is a human decision — this skill gathers the cheap signals that inform that choice, recommends a path and a sequence, and hands off. It routes, never executes: every step it recommends is invoked explicitly by a human, and each produces a reviewable artifact.
Stay shallow. The value is finishing in under a minute on a repo you have never seen. Deep vocabulary mining is /concept-extractor; behavior capture is /characterization-tests. Those are steps in the plan, not prerequisites to producing it.
Data Sources
Use whatever is present; state in the plan which were available — a plan built without git or a runnable instance is more heuristic, and must say so.
Repo probe (always)
Read-only counts and pattern hits, never comprehension:
- Platform / age — build files:
javax.* vs jakarta.*, servlet/EJB/JSF/Spring versions, target JDK; or package.json with jQuery/AngularJS/Backbone.
- Size / shape — module, package, and file counts; LOC order of magnitude; density of
*Manager/*Impl/*Util/ names (overengineering signal → concept pipeline pays off; small and clean → rearchitect directly).
