dependency-upgrade-plannerlisted

Turn "bump the version and hope" into a sequenced, evidence-backed upgrade plan. The skill establishes the exact current → target version gap, reads the CHANGELOG and migration guide for **every** major in between, then greps the codebase for the dependency's imported symbols so the breaking-change list is narrowed to the call sites that actually exist here. It checks the target's peer-dependency and runtime requirements, orders the work (codemods first, one major at a time for big jumps, behind tests), and writes down a rollback before anything is touched. ## When to use this skill - A key dependency, framework, or runtime is several majors behind and you need a path forward, not a single `npm install pkg@latest`. - A security advisory (CVE, `npm audit`, Dependabot) forces an upgrade and you need to know the blast radius before merging. - You are scoping a framework or runtime migration (React, Next.js, Django, Rails, Node, Python) and want to know what breaks before committing the sprint. > [!WARNING] > Jumping several majors in one `install` hides which version broke what. Breaking changes compound: v3's removal of an API plus v4's renamed option plus v5's changed default land as one undebuggable wall of errors. For a gap of two or more majors, upgrade **one major at a time**, landing each behind a green build/test run, so every failure maps to exactly one version's changes. ## Instructions 1. **Pin the exact current and target versions.** Read the lockfile (`package-