spatial-sdk-update

Use this skill when you need to help the user upgrade an existing PICO Spatial SDK project (especially Android/Kotlin projects) to a newer version of the PICO Spatial SDK. This involves more than just simple API name replacements; it includes dependency resolution and project configuration upgrades.

Boundary: this skill assumes the project is already a PICO Spatial/MR application. If the primary task is to transform a traditional Android phone/tablet app into Spatial containers and interaction patterns, route to porting-android-app instead.

Trigger boundary: only run this skill when the user explicitly asks to upgrade, migrate, or change the Spatial SDK version (or when a build failure they asked you to fix is unambiguously caused by an SDK version change). Upgrading the business SDK is a user-initiated action — do not proactively propose or start an SDK upgrade, and do not prompt users who only want to keep building against their current version. When you notice a newer SDK exists but the user has not asked to upgrade, at most mention it as an optional aside and continue with the current version. Environment health and CLI/plugin/PICO development knowledge version checks belong to pico-env-doctor, not here.