Upgrade Planning and Execution Readiness

Turn public Splunk guidance and supplied environment evidence into a bounded upgrade-readiness decision. Plan and assess; never perform or approve the upgrade, restart services, change configuration, schedule maintenance, execute rollback, or claim that an unevidenced check passed.

When to Use

Use this skill after a version-change request has been routed to upgrade readiness. It owns planning, rehearsal, prerequisite and compatibility review, topology-aware sequencing, backup and recovery posture, maintenance readiness, go/no-go criteria, and planned post-upgrade validation.

Keep adjacent work outside the skill. General facts without an upgrade decision belong to splunk-product-question-navigator; app-specific lifecycle or remediation belongs to the app/add-on compatibility owner; active post-upgrade symptom diagnosis belongs to a Splunk platform operations specialist; Cloud administration actions belong to a workflow that explicitly owns them. Name a route only when the answer crosses this boundary.