Claude Opus 5.5 Migration

AdvanceddevelopmentMinimum 64K context
View source

Plans and executes a migration of an Anthropic integration from Claude Opus 5 or earlier to Claude Opus 5.5. Inventories model IDs and request parameters, replaces manual extended-thinking budgets with adaptive thinking and effort levels, reviews context- window and output-limit assumptions, recalculates cost with the new pricing and cache- read rates, and defines an eval and rollout plan.

Use cases

  • Moving a production integration from Claude Opus 5 to Claude Opus 5.5
  • Replacing budget_tokens thinking configuration with adaptive thinking and effort
  • Re-estimating cost after a model price and cache-rate change
  • Planning a staged rollout with regression evals and rollback

Example prompt

Plan a migration of this integration to Claude Opus 5.5.

Context: [current model IDs, request parameters, thinking config, prompts, traffic volume]

Return:
1. Inventory of every call site and parameter that must change.
2. Thinking and effort settings per workload, with rationale.
3. Context-window and max-output assumptions to revisit.
4. Cost comparison including cache writes and reads.
5. Eval set and pass criteria before switching.
6. Staged rollout and rollback plan.

Recommended models

Compatible tools

claude-codecursorkiroany

Modalities

Input: text, code
→
Output: text, code

Related Skills

Author

OpenModels Community

@openmodelsrun

Publisher

Verified source

OpenModels Community

Adapted from the linked source

Canonical source ↗