runbooks

Create and execute incident runbooks with verification and rollback steps.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yknothing/prodcraft --skill runbooks-yknothing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbooks
Source: https://github.com/yknothing/prodcraft/tree/main/skills/07-operations/runbooks
Command: npx skills add https://github.com/yknothing/prodcraft --skill runbooks-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runbooks convert operational knowledge into concise, executable procedures that can be followed under pressure to contain incidents, verify recovery, and communicate clearly.

Core Features & Use Cases

  • Explicit triggers, owners, and escalation paths to ensure timely response.
  • Step-by-step execution with verification, rollback or safe-fail options, and communication guidance.
  • Use case: standardizing incident response for outages and major incidents across services.

Quick Start

Follow this runbook template to document the incident trigger, owner, step-by-step actions, verification checks, and post-incident communication.

Frequently Asked Questions about runbooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document an incident response runbook for production outages?

An incident response runbook documents explicit triggers, owners, and escalation paths to ensure timely response during production outages. It provides step-by-step execution guidance with verification checks, rollback options, and stakeholder communication protocols.

What is the best way to standardize operational incident playbooks across on-call rotations?

Standardizing operational incident playbooks involves converting operational knowledge into concise, executable procedures with explicit input and output contracts. This ensures responders across on-call rotations can safely contain incidents, verify recovery, and communicate clearly under pressure.

How does a runbook handle rollback considerations during an operational outage?

A runbook handles rollback considerations by providing stepwise execution processes that include predefined verification checks and safe-fail options. This guides responders to safely contain operational outages and execute recovery actions without exacerbating the incident.

Can I use this runbook template for post-incident recovery drills?

Yes, you can use this runbook template for post-incident recovery drills. It applies to production incidents, operational outages, and recovery drills by providing a standardized template to document triggers, owners, step-by-step actions, and verification checks.

What should be included in stakeholder communication guidelines during a major incident?

Stakeholder communication guidelines during a major incident should include predefined post-incident communication steps integrated within the runbook. This ensures clear, timely updates are delivered while responders execute containment, verification, and rollback actions.