WorkflowFor DevelopersDevOps & CI/CD

Production Readiness Checklist.

In the week before any production launch — this checklist prevents the most common first-day production failures.

ChatGPT · Claude · Gemini·Advanced·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 · v3
production-readiness-checklist-4.md · 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: DevOps & CI/CD
- Use case: Production Readiness Checklist
- Source task:
  - I am about to deploy {{describe_application}} to production for the first time.
  - Step 1: Checklist: generate a comprehensive production readiness checklist across: security, observability, reliability, performance, data, documentation, and operational readiness.
  - Step 2: Critical Gaps: for each section, identify the 2-3 items that, if missing, are most likely to cause a production incident in the first 30 days.
  - Step 3: Go/No-Go Decision: based on the checklist, define minimum criteria for a production launch vs. criteria that can be deferred.

# Goal
Full production readiness checklist, critical gap identification per section, and a Go/No-Go decision framework.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Full production readiness checklist, critical gap identification per section, and a Go/No-Go decision framework.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleproduction readiness reviewer
{{use_case}}Your specific valueproduction readiness checklist
{{describe_application}}Describe applicationExample describe application

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone — formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

In the week before any production launch — this checklist prevents the most common first-day production failures.

PRO TIP

Treat production readiness as a team activity, not a solo review — different engineers will catch different gaps.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

★ THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth — built by developers for developers.

Browse more prompts →