Framework Migration Deps Upgrade

---
name: framework-migration-deps-upgrade
description: "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration paths."
risk: critical
source: community
date_added: "2026-02-27"
---

# Dependency Upgrade Strategy

You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration paths for breaking changes.

## Use this skill when

- Working on dependency upgrade strategy tasks or workflows
- Needing guidance, best practices, or checklists for dependency upgrade strategy

## Do not use this skill when

- The task is unrelated to dependency upgrade strategy
- You need a different domain or tool outside this scope

## Context
The user needs to upgrade project dependencies safely, handling breaking changes, ensuring compatibility, and maintaining stability. Focus on risk assessment, incremental upgrades, automated testing, and rollback strategies.

## Requirements
$ARGUMENTS

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open `resources/implementation-playbook.md`.

## Output Format

1. **Upgrade Overview**: Summary of available updates with risk assessment
2. **Priority Matrix**: Ordered list of updates by importance and safety
3. **Migration Guides**: Step-by-step guides for each major upgrade
4. **Compatibility Report**: Dependency compatibility analysis
5. **Test Strategy**: Automated tests for validating upgrades
6. **Rollback Plan**: Clear procedures for reverting if needed
7. **Monitoring Dashboard**: Post-upgrade health metrics
8. **Timeline**: Realistic schedule for implementing upgrades

Focus on safe, incremental upgrades that maintain system stability while keeping dependencies current and secure.

## Resources

- `resources/implementation-playbook.md` for detailed patterns and examples.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

## Version, tooling and verification limits

The analyzer, compatibility checker, codemod generator and monitoring framework have many unimplemented helpers; they are design sketches, not a working audit. Distinguish npm outdated exit 1 for available updates from network/auth failure, and pip inventory of an environment from declared project dependencies. Pin the correct interpreter/lockfile. packaging.version implements Python version semantics, not npm semver ranges; use each ecosystem’s parser and mark unknown/pre-release/0.x changes for review.

Latest, minor and patch labels do not establish safety, support or security. Verify official release notes, advisories, peer/engine/OS requirements and available artifacts for the selected exact version. Upgrades may execute lifecycle scripts, codemods or migrations: inspect and isolate them first. Do not run commands merely because this playbook names them; use actual project scripts and approved registries, and avoid bypassing peer checks or updating snapshots to hide regressions. A passing build/declared dependency graph is not a compatibility certification. Budget estimates and dashboard thresholds are examples. No dependency install, codemod, migration, benchmark or rollback was executed here.