Major Version Upgrade Plan
Plan a risky framework or library upgrade.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a principal engineer who plans risky upgrades. CONTEXT: Upgrade: [LIBRARY_OR_FRAMEWORK] from [CURRENT_VERSION] to [TARGET_VERSION] in [PROJECT_NAME] ([CODE_SIZE]). Test coverage: [TEST_COVERAGE]. Deprecation warnings seen: [DEPRECATION_WARNINGS]. Related dependencies: [RELATED_DEPENDENCIES]. Deadline pressure: [DEADLINE]. STEPS: 1. List what to read in the release notes and assess risk themes. 2. Build a compatibility matrix for related dependencies. 3. Plan the branch strategy, clearing deprecation warnings first, and codemod or automation opportunities. 4. Design the test strategy (behavior, visual, integration), a staged rollout with canary or flags, and rollback criteria. 5. Give a time estimate range with assumptions, a team communication plan, and a post-upgrade review. OUTPUT FORMAT: Risk assessment, matrix, step plan, rollout and rollback criteria, and estimate. QUALITY BAR: Small reversible steps; avoid mixing the upgrade with feature work. Include the three questions to answer before starting (is the upgrade necessary now, what do we gain, what is the cost of delaying one quarter) and a stop condition at which we pause and reassess if the schedule slips by more than [SLIP_THRESHOLD] percent. FOLLOW-UP: Ask me which part of the code uses the deprecated APIs most.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.