Researchernote-taker · research master
software · collaboration · Builder 5
API migration plan
Convert an API change into one compatibility-aware implementation and rollout plan.
ONE REQUIRED OUTCOME
An inventory, contract delta, migration sequence, test matrix, rollback plan, and documentation update.
01 →02 →Coderfact-checker · security savant03 →Plannercontext-keeper · DevOps engineer04 →Testerdevils-advocate · QA tester05 Reviewerformatter · technical writer
Downloads contain assignments only—never provider keys, model choices, outputs, uploads, pairing details, or training material.
- An SDK or service endpoint is changing
- Backward compatibility matters
- Multiple consumers need an ordered migration
- The old and new contracts are both unknown
- The user wants an unreviewed production cutover
Every box owns a bounded handoff.
Researcher · note taker · heavy
research master
Inventory old and new official contracts, dates, deprecations, limits, and affected consumers.
Coder · fact checker · heavy
security savant
Map request, response, error, authentication, retry, and data-model differences.
Planner · context keeper · heavy
DevOps engineer
Design the additive migration sequence, feature flags, compatibility window, and rollback checkpoints.
Tester · devils advocate · heavy
QA tester
Write contract, integration, failure, load, and downgrade tests that prove the new path.
Reviewer · formatter · heavy
technical writer
Produce the single migration runbook and verify that every affected consumer and failure path is covered.