Use when a release, installer, schema, configuration, or tool must work for both new users and users upgrading from an older version.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add ShugokiFable/Ultimate-AI-Starter-Bundle --skill upgrade-path-testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Upgrade Path Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/shugokifable-upgrade-path-testing)More formats (shields.io, HTML) on the badges page.
---
name: upgrade-path-testing
description: Use when a release, installer, schema, configuration, or tool must work for both new users and users upgrading from an older version.
---
# Upgrade Path Testing
A **fresh install** and an **upgrade** are different products. Prove both.
## Contract
Test at least:
1. empty profile → current version;
2. previous version (supported) → current version;
3. partially configured previous install → current version;
4. rerun current installer over current version.
For upgrades, preserve user-owned configuration, credentials, caches worth retaining, project data, and unrelated files. Replace only bundle-owned state. Validate migrations before deleting old data and keep rollback/backup material until the new state passes its doctor.
Compare the post-upgrade effective configuration with a fresh install plus the user's intentional customizations. A successful fresh install does not prove the upgrade path.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...