SDK Migration Guide Generation with Claude Code: API Runtime Pattern
A production playbook for SDK migration guide generation in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Developer experience teams
The problem
Developer experience teams need SDK migration guide generation to run repeatedly against old SDK docs, new SDK docs, examples, and changelogs. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the SDK migration guide generation instructions as a skill, send old SDK docs, new SDK docs, examples, and changelogs as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For SDK migration guide generation, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=sdk-migration-guide
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo