eng-runbook

Create structured engineering runbooks with service summaries, alerts, and incident-response checklists.

3|2|Updated May 28, 2026
One-click install
npx skills add https://github.com/Clos01/Kenbun-Agent --skill eng-runbook-clos01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-runbook
Source: https://github.com/Clos01/Kenbun-Agent/tree/main/core/tools/skills/eng-runbook
Command: npx skills add https://github.com/Clos01/Kenbun-Agent --skill eng-runbook-clos01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn scattered operational knowledge into structured engineering runbooks that improve incident response, service ownership, and on-call readiness.

Core Features & Use Cases

  • Service Documentation Structure: Creates single-page runbooks with service summaries, ownership details, dependencies, alerts, dashboards, and operational procedures.
  • Incident Response Guidance: Produces on-call checklists, escalation flows, and recovery steps for production incidents.
  • Use Case: An engineering team can use this Skill to document an authentication service with deployment procedures, rollback steps, alert handling, and rotation schedules.

Quick Start

Create a production runbook for our service with alerts, dashboards, procedures, on-call rotation, and incident response steps.

Frequently Asked Questions about eng-runbook

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

FAQPage Schema
What is an engineering runbook and when do I need one for incident response?

An engineering runbook is a structured document containing service summaries, alert tables, and incident response checklists. You need one to improve on-call readiness and standardize operational procedures for production service management.

How do I create a production runbook for on-call service documentation?

To create a production runbook, provide formatted service summaries, dashboard references, executable procedure examples, and incident response checklists. This generates structured operational documentation covering deployment procedures, rollback steps, and alert handling.

Can I use this to document SRE escalation flows and recovery steps for production incidents?

Yes, this generates incident response guidance including on-call checklists, escalation flows, and recovery steps for production incidents. It structures operational procedures specifically for SRE and DevOps service ownership scenarios.

Does this work for DevOps teams needing single-page service documentation with dependencies and alerts?

Yes, this creates single-page runbooks with service summaries, ownership details, dependencies, alerts, and dashboards. It is designed for DevOps and SRE teams requiring operational readiness documentation.

What is the best way to structure operational procedures and on-call guides for a microservice?

The best way to structure operational procedures is using formatted service summaries, alert tables, executable procedure examples, and incident response checklists. This ensures operational readiness for on-call guides and recovery workflows.

What should I not use a structured runbook for in software engineering operations?

Structured runbooks should not replace dynamic monitoring or automated alerting systems. They are static documentation for on-call guides and incident response workflows, requiring manual updates to reflect service changes and deployment procedures.