Writing a change request with AI: the prompt and the template
The change request template that holds up in review, the prompt that fills it, and where to push hardest: the backout plan and the risk section.
A good change request is mostly structure plus honesty about what could go wrong. Both are things AI is well suited to draft, as long as you drive it properly. Here is the template, and the prompt to fill it.
The template. Summary. Reason or business driver. Scope, in and out. Implementation steps. Backout plan. Risk assessment, one row per risk with likelihood, blast radius, and a mitigation or pre-check. Validation, how you confirm success. Affected systems and stakeholders. Proposed window.
The prompt. Give the AI one sentence describing the change and ask it to draft every section above, and to ask you up to three questions where it cannot fill a section responsibly rather than guessing. Answer the questions, then have it regenerate. Example input: "Upgrade the prod database primary from major version 14 to 16 during the Sunday window."
Where to push hardest: the backout plan. Weak change requests say "roll back if there are issues." Make the AI write exact reversal steps, how long they take, the point of no return if there is one, and how you verify the rollback actually worked. If it cannot produce a real backout, that is a signal about the change itself.
The risk section. Ask specifically for realistic failure modes including partial failure and "it worked but broke something adjacent," not just the obvious one. Each with likelihood, blast radius, and a pre-check that would catch it.
Then challenge your own request. Paste the finished draft back and ask the AI to review it as a skeptical change-approval board: unstated assumptions, gaps in the backout, risks not accounted for, missing stakeholders, whether the window and validation are adequate. Fix what it finds before you submit.
After the change: have it turn the request into a validation checklist to run immediately and again 24 hours later, covering the thing you changed and the adjacent systems that could be affected.
Get the prompts
Five of these, written out in full with the fill-ins and guardrails already in them, are free on GitHub. No email needed.
A sixth, the postmortem prompt with a complete worked example, comes free by email.
Get the postmortem prompt See the five free prompts
All 42, organized by the job in front of you, are $9: the Cronhaven Ops Prompt Library.