What problem does it solve?
Writing a safe, concrete migration plan (e.g., CommonJS to native ESM, Python 2 to 3, Vue 2 to 3) requires knowing the exact source and target stacks, finding authoritative migration guides, and checking the current repository state. This meta-skill orchestrates that entire workflow so the user receives one dense, actionable checklist instead of piecing together research manually.
Core Features & Use Cases
- Migration Intake & Clarification: Extracts source stack, target stack, version context, and repo scope from the request, and asks the user a structured clarification form when key fields are missing.
- LLM Classification: Tags the request as one of PY2_TO_PY3, VUE2_TO_VUE3, REACT_CLASS_TO_HOOKS, OPENAI_V0_TO_V1, CJS_TO_ESM, or OTHER, with hard overrides so explicit user wording wins over noisy context.
- Guide Lookup & Repo Context: Routes to the multi-search-engine skill for authoritative migration guides and optionally inspects the current git diff when the request references local changes.
- Constrained Plan Writer: Produces a Markdown checklist with Summary, Evidence boundary, Breaking changes, Step-by-step, Repository discovery, grep patterns, read-only Validation commands, and Rollout/rollback sections.
- Use Case: A user asks "Give me a practical migration checklist to move my package from CommonJS to native ESM" and receives a 1,200-1,800 word plan with copyable
git grep discovery commands, Node version caveats, and dual-publish rollout decision points.
Quick Start
Ask the agent to create a migration plan, for example: "Create a step-by-step migration checklist to migrate my Node package from CommonJS to native ESM, including validation and rollback steps."
