Prompt that plans schema and API changes in compatible phases without breaking old clients. Paste it into an AI tool of your choice, which then plans compatible schema changes.
Results depend on the tool, the model and what you enter.
Fill in
What you type stays in this browser window. We store and send nothing.
What should change?
new optional field
rename a field
change type or format
remove a field or endpoint
reshape the response
Who depends on it?
own web app
mobile apps
external partners
background jobs
mixed
How urgent?
soft window
fixed date
hotfix
gradual over weeks
unclear
Your prompt
Help me plan a schema or API change so existing clients and readers do not break.
Change: [Change]
Consumers: [Consumers]
Deadline: [Deadline]
Steps: 1. Read today's schema, the planned change and which clients or jobs read and write which fields. 2. Check whether the change only adds fields, renames, changes a type or removes something. 3. Propose an order: compatible extensions first, then dual write or dual read, and only then removal. 4. Define how defaults and unknown fields are handled and whether version numbers or negotiation headers are needed. 5. List tests for old and new clients and a rollback plan. 6. Write a short note to teams that must adapt, with a date and what stays unchanged.
Output: compatibility matrix, migration order, test plan, rollback and notice text.
Take particular care to extend first, remove last, and keep old clients working the whole time.
Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.
You have edited the prompt. Changes in the fields above no longer overwrite it.
This is an instruction for an AI, not the result itself.
Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
Copy the finished prompt into an AI tool of your choice.
Paste current and planned schema, a list of known clients and sample requests and responses, without secrets.
Why does this work?
Renaming a field and deleting the old one at the same time breaks quiet clients. Dual writing and reading first lets you clean up later without downtime.
Tips
Keep old fields for at least one full release period after nothing writes them anymore.
Prompt that plans a data backfill in small, resumable batches with clear brakes.
Prompt · Intermediate · about 15 min
You may use our prompts freely, including at work. Please do not republish them as your own collection. We give no warranty for AI results; check them yourself. Terms of use
