Grok Bot DevOps prompts that stop before the deploy
Incident packs, runbook drafts, deploy notes, and on-call handoffs. Distinct from engineering code and PRs, and from security approvals. The Bot does not deploy, restart production, or page people. You still do.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Incident packs
5 promptsIncident commander pack
1/21✨ What it does
The Bot builds an incident commander pack for [INCIDENT] from monitoring, Slack, deploys, and status, with facts, unknowns, and a suggested next check. You still page people and you still change production.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build an IC pack for [INCIDENT] between [START] and [END]. Facts vs unknowns. Do not page. Do not change production. Sources: [MONITORING], [SLACK INCIDENT], [DEPLOYS], [STATUS PAGE READ ONLY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not resolve the incident in the tool. Do not invent blast radius. Deliverable: Window, symptoms, facts, unknowns, links, suggested next human check. Review point: I run the incident. I page. I change prod.
Pro tip: Pin the window. A pack without start and end times becomes a history of the service.
Customer-impact note
2/21✨ What it does
The Bot drafts a customer-impact note for [INCIDENT] from [MONITORING] and [SUPPORT QUEUE], listing who is hurt and what is still unknown. You still publish status and you still page the comms owner.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft customer impact for [INCIDENT] from [MONITORING] and [SUPPORT QUEUE]. No invented ETA. Do not publish status. Do not page. Sources: [MONITORING], [SUPPORT QUEUE], [STATUS PAGE READ ONLY], [INCIDENT CHANNEL]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not publish the status page. Do not email customers. Deliverable: Who is hurt, what we know, what is unknown, draft status lines. Review point: I publish status. I page comms.
Pro tip: Unknown is allowed. A fake ETA on a status page is worse than a late one.
War-room channel brief
3/21✨ What it does
The Bot writes a war-room brief for [INCIDENT] from [#CHANNEL] and [TOOLS], listing who is in, what was tried, and open questions. You still page the next person and you still restart services.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Brief [#CHANNEL] for [INCIDENT]: who is in, what was tried, open questions. Do not page. Do not restart. Sources: [#CHANNEL], [MONITORING], [DEPLOYS], [TICKETS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not post back to the channel without approval. Deliverable: Present people, tried steps with times, open questions, links. Review point: I page the next person. I restart if needed.
Pro tip: Quote the try and the timestamp. A vibe of "we tried a lot" hides the next check.
Severity call draft
4/21✨ What it does
The Bot drafts a severity call for [INCIDENT] against [SEV RUBRIC] from current symptoms and blast radius, and writes unknown when a source is missing. You still set the sev and you still page the rotation.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft sev for [INCIDENT] against [SEV RUBRIC]. Unknown if a source is missing. Do not set sev in the tool. Do not page. Sources: [SEV RUBRIC], [MONITORING], [SUPPORT VOLUME], [CUSTOMER LIST IF ALLOWED]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not change the incident sev in the tool. Do not invent customer counts. Deliverable: Suggested sev, rubric lines used, evidence, unknowns. Review point: I set the sev. I page the rotation.
Pro tip: Paste the rubric. "This feels like a SEV1" without a rule is theater.
Vendor status during an incident
5/21✨ What it does
The Bot checks [VENDOR STATUS PAGES] and [DEPENDENCY LIST] during [INCIDENT] and lists which third parties are actually degraded, with links. You still page the vendor and you still fail over.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Check [VENDOR STATUS PAGES] and [DEPENDENCY LIST] for [INCIDENT]. Which are degraded. Links. Do not page the vendor. Do not fail over. Sources: [VENDOR STATUS URLS], [DEPENDENCY LIST], [MONITORING]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not open a vendor ticket as me. Do not fail over traffic. Deliverable: Vendor, status, as-of, link, ours vs theirs, suggested human next step. Review point: I page the vendor. I fail over.
Pro tip: Open the vendor page. A tweet screenshot is not a status.
Runbook drafts
4 promptsNew runbook from the last fire
6/21✨ What it does
The Bot drafts a runbook for [SERVICE OR ALERT] from [LAST INCIDENT NOTES] and the live tool UI, with steps a human can follow. You still run the steps and you still restart production.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a runbook for [SERVICE OR ALERT] from [LAST INCIDENT NOTES] and the live tool UI. Do not run the steps. Do not restart. Sources: [LAST INCIDENT NOTES], [TOOL UI], [EXISTING RUNBOOKS IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not publish the runbook. Do not execute recovery steps. Deliverable: Draft path, steps, screenshots, owner, definition of done. Review point: I publish the runbook. I run it.
Pro tip: Click the real UI. A runbook written from memory will lie on the first page.
Runbook versus the last incident
7/21✨ What it does
The Bot compares [RUNBOOK] to what actually happened in [INCIDENT] and lists missing steps, stale screenshots, and unsafe shortcuts. You still edit the wiki and you still deploy the fix.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [RUNBOOK] to [INCIDENT]. Missing steps, stale shots, unsafe shortcuts. Do not edit the wiki. Do not deploy. Sources: [RUNBOOK], [INCIDENT TIMELINE], [TOOL UI]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not edit the live runbook. Do not run the stale steps. Deliverable: Step, doc vs what happened, screenshot, keep / rewrite / delete. Review point: I edit the wiki. I deploy the fix.
Pro tip: This is gap vs the fire, not a UI cosmetics pass. Ops already has click-the-tool drift.
Tabletop exercise pack
8/21✨ What it does
The Bot writes a tabletop pack for [FAILURE SCENARIO] using [RUNBOOKS] and [ON-CALL ROSTER], with injects and expected decisions. You still run the drill and you still page if it goes live.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a tabletop pack for [FAILURE SCENARIO] from [RUNBOOKS] and [ON-CALL ROSTER]. Injects and expected decisions. Do not page. Do not touch prod. Sources: [RUNBOOKS], [ON-CALL ROSTER], [LAST INCIDENTS], [SEV RUBRIC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not create a real incident. Do not page the rotation for the drill. Deliverable: Scenario, inject timeline, expected calls, gaps in the runbooks. Review point: I run the drill. I page only if it is real.
Pro tip: Name the failure. "Practice an outage" without a scenario is a meeting with snacks.
Break-glass access notes
9/21✨ What it does
The Bot lists break-glass steps for [SYSTEM] from [ACCESS DOC], including who must approve and what gets audited. You still request access and you still deploy with it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List break-glass steps for [SYSTEM] from [ACCESS DOC]. Who approves, what is audited. Do not request access. Do not deploy. Sources: [ACCESS DOC], [SSO OR VAULT READ ONLY], [AUDIT POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not request or grant break-glass. Do not copy production secrets. Deliverable: Steps, approver, audit trail, risky lines, questions for me. Review point: I request access. I deploy if I must.
Pro tip: If the doc says dump prod, stop and tell you. That is the point of the brief.
Deploy and change notes
4 promptsChange-window brief
10/21✨ What it does
The Bot writes a change-window brief for [DEPLOY] from [TICKET], [CI], and [DEPENDENCIES], with risk, rollback, and who must be awake. You still deploy and you still page if it fails.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Change-window brief for [DEPLOY]: risk, rollback, who must be awake. Do not deploy. Do not page. Sources: [TICKET], [CI], [DEPENDENCIES], [ON-CALL ROSTER], [LAST SIMILAR DEPLOY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not merge, promote, or start the window. Deliverable: Window, risk, rollback, awake people, go / hold suggestion. Review point: I deploy. I page if it fails.
Pro tip: Name who is awake. A Friday deploy with no rollback owner is a weekend incident.
Rollback plan from the last release
11/21✨ What it does
The Bot drafts a rollback plan for [RELEASE] from [DEPLOY LOG] and [RUNBOOK], with the first safe reverse step and what would make rollback worse. You still roll back and you still page the owner.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft rollback for [RELEASE] from [DEPLOY LOG] and [RUNBOOK]. First safe reverse step. What makes it worse. Do not roll back. Do not page. Sources: [DEPLOY LOG], [RUNBOOK], [CI], [FEATURE FLAGS READ ONLY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not roll back, revert, or flip flags. Deliverable: First reverse step, blockers, worse-if, owner, links. Review point: I roll back. I page the owner.
Pro tip: First safe reverse step only. A 12-step rollback no one has run is a second incident.
Canary and flag notes
12/21✨ What it does
The Bot writes canary and flag notes for [CHANGE] from [FLAG TOOL] and [METRICS], including abort signals. You still flip the flag and you still deploy the next step.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Canary and flag notes for [CHANGE] from [FLAG TOOL] and [METRICS]. Abort signals. Do not flip. Do not deploy. Sources: [FLAG TOOL READ ONLY], [METRICS], [CHANGE TICKET], [ROLLBACK NOTE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not flip flags. Do not change percentages. Do not promote the canary. Deliverable: Flag, current %, abort signals, metrics links, suggested hold or go. Review point: I flip the flag. I deploy the next step.
Pro tip: Write the abort signal before the flip. "Watch it" is not a canary plan.
Infra change ticket pack
13/21✨ What it does
The Bot builds a change ticket pack for [INFRA CHANGE] from [PLAN FILE] and [CLOUD CONSOLE], read-only, with blast radius and a do-not-apply line. You still apply the plan and you still restart nodes.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Change ticket pack for [INFRA CHANGE] from [PLAN FILE] and [CLOUD CONSOLE]. Blast radius. Do not apply. Do not restart. Sources: [PLAN FILE], [CLOUD CONSOLE READ ONLY], [TICKET], [DEPENDENCIES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not apply Terraform or cloud changes. Do not resize or restart nodes. Deliverable: Change, blast radius, rollback, do-not-apply line, links, unknowns. Review point: I apply the plan. I restart nodes.
Pro tip: Read-only console. Applying a plan from the Bot computer is a production write.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
On-call packs
4 promptsShift handoff pack
14/21✨ What it does
The Bot writes an on-call handoff for [SHIFT] from [PAGER], [OPEN INCIDENTS], and [SILENCED ALERTS], with what is lingering. You still take the pager and you still page if a fire is open.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Handoff for [SHIFT] from [PAGER], open incidents, silenced alerts. What is lingering. Do not ack. Do not page. Sources: [PAGER], [OPEN INCIDENTS], [SILENCED ALERTS], [SLACK #incidents]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not ack, silence, or resolve alerts. Do not take the pager in the tool. Deliverable: Open fires, silenced older than [N] hours, leftover work, suggested first action for me. Review point: I take the pager. I page if a fire is open.
Pro tip: Lingering silenced alerts are the ones that bite the next person. List them.
Pager noise weekly
15/21✨ What it does
The Bot ranks noisy pages for [TEAM] over [WINDOW] from [PAGER] and names likely flappers, without silencing anything. You still silence alerts and you still page on real fires.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rank noisy pages for [TEAM] over [WINDOW] from [PAGER]. Name likely flappers. Do not silence. Do not page. Sources: [PAGER], [ALERT DEFS], [DEPLOYS IN WINDOW]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not silence, ack, or delete alert rules. Deliverable: Alert, count, last deploy nearby, flapper yes/no/unknown, suggested human fix. Review point: I silence or rewrite the alert. I page on real fires.
Pro tip: Cap the list. A dump of every page is how the real flapper hides.
Coverage gaps on the rotation
16/21✨ What it does
The Bot checks [ON-CALL SCHEDULE] for the next [N] days and lists gaps, double-bookings, and missing backups. You still edit the rotation and you still page the backup.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Check [ON-CALL SCHEDULE] for the next [N] days. Gaps, double-bookings, missing backups. Do not edit the schedule. Do not page. Sources: [ON-CALL SCHEDULE], [TIME OFF], [ESCALATION POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not edit the rotation. Do not override who is on call. Deliverable: Date, gap or double, missing backup, suggested fill, evidence. Review point: I edit the rotation. I page the backup if needed.
Pro tip: Primary without a backup is a gap. "They will see Slack" is not coverage.
Escalation tree draft
17/21✨ What it does
The Bot drafts an escalation tree for [SERVICE] from [ROSTER] and [RUNBOOK], with who to call after [N] minutes. You still page up the tree and you still decide when to escalate.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft an escalation tree for [SERVICE] from [ROSTER] and [RUNBOOK]. Who after [N] minutes. Do not page. Do not change the live policy. Sources: [ROSTER], [RUNBOOK], [CURRENT ESCALATION POLICY], [SEV RUBRIC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not page up. Do not edit the live escalation policy. Deliverable: Level, person or role, after minutes, backup, gaps. Review point: I page up the tree. I edit the live policy.
Pro tip: Minutes, not "if it feels bad". A tree without a clock is a group chat.
Make the DevOps Bot durable
4 promptsDevOps Bot description
18/21✨ What it does
The Bot writes a DevOps Bot description named [NAME] that drafts packs from dashboards and runbooks and never deploys, restarts, or pages. You still create the Bot and you still hold the pager.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a DevOps Bot description named [NAME] for incident packs, runbooks, deploy notes, and on-call handoffs. Never deploy, restart, or page. Sources: [DASHBOARDS], [PAGER], [RUNBOOKS], [REVIEW WINDOW]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not create the Bot until I paste the description. Deliverable: Description, pack format, never-do. Review point: I create the Bot. I hold the pager.
Pro tip: Write the never-deploy line in the description, not only in one chat.
Weekday infra digest routine
19/21✨ What it does
The Bot writes a weekday routine that posts an infra digest for [SERVICES] from [DASHBOARDS] at [TIME TZ] and changes nothing if a board is down. You still enable it and you still deploy or page from it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekdays at [TIME TZ], post an infra digest for [SERVICES] from [DASHBOARDS]. Fail closed if a board is down. Do not deploy. Do not page. Sources: [DASHBOARDS], [PAGER], [DEPLOYS], [ERROR TRACKER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not enable the routine. Do not restart, scale, or change alerts when a chart looks wrong. Deliverable: Routine card, digest format, last-good behavior. Review point: I enable it after one dry run. I deploy or page from it.
Pro tip: Fail closed. A pretty digest built on one live board is how you miss the outage.
What DevOps Bots never do
20/21✨ What it does
The Bot writes a never-do list for DevOps Bots from [RULES], covering deploy, restart, page, silence, and production writes, plus the human substitute. You still paste it and you still do those actions yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for DevOps Bots from [RULES]. Include no deploy, no restart, no page, no silence, no production writes. Sources: [RULES] and my extras: [LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not paste into other Bots until I say so. Deliverable: 12 never-do items and the human substitute. Review point: I paste it into every DevOps Bot.
Pro tip: Paste this next to the engineering and security never-do lists. They share one computer.
Roster: who drafts versus who deploys
21/21✨ What it does
The Bot writes a roster note that splits [DRAFT BOT] from the humans who deploy, restart, and page for [TEAM]. You still assign the Bots and you still hold the pager.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Roster note: [DRAFT BOT] drafts packs. Humans on [TEAM] deploy, restart, and page. I assign. I hold the pager. Sources: [TEAM ROSTER], [BOT LIST], [APPROVAL POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not deploy. Do not restart production. Do not page anyone. - Do not create Bots or change who is on call. Deliverable: Draft Bot, human deployers, human pager, approval line. Review point: I assign the Bots. I hold the pager.
Pro tip: A Bot that drafts the rollback must not be the one that runs it.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides