DevOps & Cloud
Operations work benefits from checklists and clear runbooks. These prompts help you plan CI and CD pipelines, monitoring and alerting, infrastructure as code, container deployments and incident response. Describe your stack, environments and constraints, and receive structured designs, review questions and draft runbooks. They suit small engineering teams and solo developers who need a sound starting point. Generated configuration must be reviewed by someone who understands your systems, tested in a non-production environment, and checked for secrets, permissions and cost before use. Never paste credentials or private infrastructure details into an AI tool.
- CI and CD 15
- Infrastructure as Code 14
- Monitoring and Alerting 15
- Incident Response 13
- Containers and Deployment 12
Start with these
A short list of well-specified prompts from this page, picked by our checklist score (specific inputs, clear output format, concrete steps). It is a heuristic, not a verdict.
-
Deployment Strategy Comparison: Rolling, Blue-Green, Canary
Compare rolling, blue-green and canary deployments for your app, traffic, risk and database changes, then pick one.
-
Alert Design: Fewer, Better Alerts
Redesign noisy alerts with a test of whether each one needs a human now, using your firing history and on-call setup.
-
On-Call Handbook for a Small Team
Write an on-call handbook for a small team covering handover, first checks, escalation and status communication.
-
Cloud Cost Control Plan for a Small Team
Create a cloud cost control plan for a small team from your bill breakdown, environments and utilisation data.
-
Infrastructure Cost Guardrails
Design cloud cost guardrails: a tagging standard, per-team budgets with 50, 80 and 100 percent alerts, and controls against surprise bills.
-
Terraform Module Structure Review
Review your Terraform or other IaC layout for module boundaries, duplication, variable hygiene and state separation by environment.
Prompts
-
CI Pipeline Design From Repository Facts
Design stages, caching and gates for a new pipeline.
-
Flaky Test Triage Protocol
Find, classify and fix intermittent CI failures.
-
Branching and Release Strategy Chooser
Compare trunk-based and release-branch models for your team.
-
Deployment Pipeline Safety Gates
Define checks that must pass before production.
-
Pipeline Secrets Handling Review
Check how a pipeline stores and exposes secrets.
-
Monorepo CI Optimisation Plan
Run only what changed and keep builds fast.
-
Rollback and Roll-Forward Runbook
Write a deployment rollback plan that actually works.
-
Preview Environments for Pull Requests
Design short-lived environments per pull request.
-
Build Reproducibility Audit
Check whether builds produce the same output twice.
-
Dependency Update Automation Policy
Set rules for automated dependency pull requests.
-
Continuous Delivery Maturity Assessment
Score where your delivery practice stands.
-
Release Notes and Changelog Automation
Generate readable release notes from commits and issues.
-
Feature Flag Lifecycle Policy
Control flag sprawl and risk.
-
Release Checklist and Go/No-Go Meeting
Standardise what must be true before shipping.
-
Deployment Strategy Comparison: Rolling, Blue-Green, Canary
Compare rolling, blue-green and canary deployments for your app, traffic, risk and database changes, then pick one.
-
Dockerfile Review and Hardening
Improve image size, speed and safety.
-
Kubernetes Manifest Review Checklist
Check workloads for reliability and security.
-
Container Image Vulnerability Triage
Prioritise scan results sensibly.
-
Zero-Downtime Deployment Plan
Plan rolling, blue-green or canary releases.
-
Container Resource Sizing Guide
Set requests and limits from evidence.
-
Local Development Environment With Containers
Standardise dev environments across a team.
-
Service Mesh or Ingress Decision Memo
Decide how traffic enters and moves in a cluster.
-
Helm Chart or Template Quality Review
Improve reusable deployment templates.
-
Database Migration Deployment Strategy
Ship schema changes without outages.
-
Backup and Restore Verification Plan
Prove that backups work.
-
Platform Team Service Catalogue Draft
Define what an internal platform offers teams.
-
Container Registry and Artifact Policy
Control images and packages from build to deploy.
-
Incident Commander Playbook
Define roles and steps for managing an incident.
-
Blameless Postmortem Writer
Turn incident notes into a learning document.
-
On-Call Handoff Template
Pass context between on-call shifts reliably.
-
Severity Classification Matrix
Make severity levels clear and consistent.
-
Incident Tabletop Exercise Script
Run a safe simulation of an outage.
-
Security Incident Response Plan Outline
Prepare for a suspected compromise at your organisation.
-
Customer Communication After an Outage
Write honest updates and a follow-up.
-
Runbook Gap Analysis After an Incident
Find missing documentation and tools.
-
Post-Incident Action Item Tracker
Make sure the follow-up actually happens.
-
Chaos Experiment Plan
Test resilience safely with a small experiment.
-
Escalation Policy Design
Define who gets paged and when.
-
Postmortem Facilitation Guide
Run a blame-free review that leads to change.
-
Incident Communication Templates for Customers
Prepare calm and factual updates.
-
Terraform Module Structure Review
Review your Terraform or other IaC layout for module boundaries, duplication, variable hygiene and state separation by environment.
-
IaC Change Review Checklist
Review infrastructure pull requests like a careful engineer.
-
Cloud Networking Design Brief
Plan a network layout with segmentation.
-
Environment Parity Plan
Reduce differences between dev, staging and production.
-
Infrastructure Cost Guardrails
Design cloud cost guardrails: a tagging standard, per-team budgets with 50, 80 and 100 percent alerts, and controls against surprise bills.
-
Disaster Recovery Plan Outline
Define recovery objectives and procedures.
-
Configuration Drift Detection Plan
Find and fix manual changes to infrastructure.
-
Policy as Code Starter Set
Write guardrail policies for infrastructure changes.
-
Secrets and Config Management Design
Separate configuration, secrets and code.
-
Infrastructure Documentation Template
Make infrastructure understandable to new engineers.
-
Cloud Account Structure Planner
Plan accounts, projects and permissions.
-
Serverless vs Containers Decision Aid
Choose a compute model with explicit trade-offs.
-
Infrastructure as Code Repository Layout
Organise modules, environments and state sensibly.
-
Cloud Cost Control Plan for a Small Team
Create a cloud cost control plan for a small team from your bill breakdown, environments and utilisation data.
-
Service Level Objectives From User Journeys
Define SLIs, SLOs and error budgets for a service.
-
Alert Noise Reduction Audit
Cut pager noise and keep the alerts that matter.
-
Dashboard Design Brief for On-Call Use
Build dashboards that answer questions quickly during an incident.
-
Log Strategy and Retention Plan
Decide what to log, where, and for how long.
-
Synthetic Monitoring Plan
Probe critical journeys from the outside.
-
Capacity Planning Worksheet
Forecast resource needs from growth and load tests.
-
Alert Runbook Template and Examples
Write runbooks that make alerts actionable.
-
Tracing and Observability Adoption Roadmap
Add tracing and correlation in stages.
-
Uptime Status Page and Communication Plan
Plan how to tell users about incidents.
-
Metrics Naming and Cardinality Guide
Keep metrics useful and affordable.
-
Error Tracking Triage Workflow
Organise exceptions into fixable work.
-
Database Monitoring Checklist
Know what to watch for a production database.
-
Alert Design: Fewer, Better Alerts
Redesign noisy alerts with a test of whether each one needs a human now, using your firing history and on-call setup.
-
Logging Standards and What Not to Log
Make logs useful and safe.
-
On-Call Handbook for a Small Team
Write an on-call handbook for a small team covering handover, first checks, escalation and status communication.
No prompts match those filters.