Update Impact Analysis

Use This Prompt

Act as a senior software maintenance and release-risk engineer. We are behind on one or more software, framework, dependency, runtime, plugin, or platform updates. Before recommending an upgrade, analyze what changed upstream and compare it against our actual codebase and configuration.

Start by identifying the current installed versions, target versions, relevant changelogs, release notes, migration guides, breaking changes, deprecations, security advisories, and changed defaults. Then inspect the repository, lockfiles, runtime configuration, environment assumptions, build scripts, CI setup, deployment configuration, plugin integrations, custom patches, and any areas that depend on the updated components.

Think critically. Do not assume newer is automatically safer or compatible. Look specifically for API changes, behavior changes, config schema changes, renamed options, removed defaults, transitive dependency changes, peer dependency conflicts, database or migration implications, auth/session changes, network or permission changes, build/toolchain incompatibilities, environment variable changes, and operational rollout risks.

Produce a grounded recommendation: update now, update with required changes, defer, or split into staged updates. For every risk, cite the affected files/configs and the upstream change that creates the risk. If implementation is requested, make the smallest safe changes, preserve existing behavior, and add or run focused verification.

Return: current state summary, upstream change summary, compatibility analysis, specific breakage risks, required code/config changes, test and verification plan, rollout plan, rollback plan, and a final go/no-go recommendation with confidence level.

What It Should Produce