runbook

To generate an on-call runbook after a production deploy, run /runbook. It reads the codebase, deploy configuration, and health checks to produce RUNBOOK.md with verified environment variables, failure modes, alert response, and rollback steps.

A production runbook is an operational reference for incident response that should include health endpoint behavior, common failure modes with fixes, required environment variables, alert response guidance, and explicit rollback steps to reduce recovery time.

Document rollback steps and health checks by reading the deployed codebase and configuration. The runbook generation process extracts health check implementation details and creates explicit rollback instructions based on the actual production deploy configuration.

Yes, you can create an incident response runbook by analyzing the existing codebase, deploy configuration, health check implementation, and .env.example file. This ensures the runbook reflects real deployed configuration with verified required environment variables.

Verifying environment variables ensures the on-call runbook is only considered complete when production is correctly configured. This prevents first responders from encountering missing configuration during incidents and reduces downtime.

The best way to reduce recovery time is generating an operational runbook that answers first-responder questions during incidents. It provides alert response guidance, common failure modes with fixes, and explicit rollback steps based on the actual production deploy.