runbook

Generate runbook skeletons from validated templates for incidents and operational tasks.

198|19|Updated May 7, 2026

Search Tags:#automation #devops #documentation #runbook #on-call #incident-management #operational-procedure

Ready to run

npx skills add https://github.com/testdouble/han --skill runbook-testdouble

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: runbook
Source: https://github.com/testdouble/han/tree/main/han-core/skills/runbook
Command: npx skills add https://github.com/testdouble/han --skill runbook-testdouble

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams create and update standardized, operable runbooks for incidents and routine operational tasks using a single, reusable template.

Core Features & Use Cases

Generates a complete runbook skeleton from a validated template, including Symptoms, Prerequisites, Resolve, Verify, Escalate, and Rollback sections.
Enforces mandatory metadata (severity, triggers, reversible, last edited, last validated) to ensure auditability and governance.
Supports per-service or alert-keyed organization and easy updates after incidents, post-mortems, or recurring tasks.

Quick Start

Draft a runbook for a real incident or recurring task using the provided template.

Frequently Asked Questions about runbook

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

FAQPage Schema

How do I create a standard incident runbook for on-call operations?▼

To create an incident runbook, you need to generate a complete skeleton from a validated template covering Symptoms, Prerequisites, Resolve, Verify, Escalate, and Rollback sections. This ensures consistent operational procedures for live-ops incidents and recurring maintenance tasks.

What mandatory metadata should an operational runbook include for auditability?▼

An operational runbook must include mandatory metadata such as severity, triggers, reversible status, last edited, and last validated dates. This metadata enforces governance and tracks the validation history of incident response procedures.

How do I organize runbooks for per-service or alert-keyed incident management?▼

You can organize runbooks by structuring them per-service or alert-keyed to match specific operational triggers. This allows easy updates and retrieval of incident documentation after post-mortems or recurring maintenance tasks.

Can I update existing post-incident documentation using a reusable runbook template?▼

Yes, you can update existing post-incident documentation using a single reusable template. The runbook generation process supports easy updates after incidents, post-mortems, or recurring tasks to maintain standardized operational procedures.

What sections are required when automating the creation of end-to-end runbooks?▼

Automating the creation of end-to-end runbooks requires sections for Symptoms, Prerequisites, Resolve, Verify, Escalate, and Rollback. These sections form the complete runbook skeleton necessary for thorough incident management and operational task documentation.