create-operational-runbook

Name: create-operational-runbook
Availability: InStock
Author: constellize

Generate incident runbooks with investigation, resolution, and rollback procedures.

1|Updated Feb 16, 2026

Search Tags:#documentation #runbook #on-call #sre #incident #ops

Ready to run

npx skills add https://github.com/constellize/marketplace --skill create-operational-runbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-operational-runbook
Source: https://github.com/constellize/marketplace/tree/main/plugins/constellize-operations/skills/create-operational-runbook
Command: npx skills add https://github.com/constellize/marketplace --skill create-operational-runbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operational incidents require fast, repeatable response procedures. This skill generates comprehensive runbooks that translate system knowledge into actionable, guided steps for on-call engineers, reducing ambiguity during outages.

Core Features & Use Cases

End-to-end runbook templates covering header, quick reference, overview, investigation procedure, resolution procedures, post-resolution steps, and maintenance
Cross-reference with system architecture and dependencies to ensure runbooks reflect current design
Includes explicit prerequisites, verification steps, rollback paths, and success criteria to keep responses safe and auditable

Quick Start

Provide the incident context (system and scenario) and I will generate a complete, ready-to-use runbook with header, investigation steps, resolution procedures, and post-resolution actions.

Frequently Asked Questions about create-operational-runbook

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

FAQPage Schema

How do I create an operational runbook for on-call incident response?▼

To create an operational runbook, provide your incident context and system scenario to generate a complete document with headers, investigation procedures, resolution steps, and post-resolution actions tailored for on-call engineers.

What should be included in an SRE runbook to guide incident resolution?▼

An SRE runbook should include explicit prerequisites, investigation procedures, resolution commands, verification steps, rollback paths, success criteria, and cross-references to design docs to ensure safe and auditable incident responses.

What is the best way to document rollback procedures and verification steps for operational incidents?▼

The best way to document rollback procedures is to structure them within a comprehensive runbook that explicitly defines resolution actions, verification commands, and success criteria to eliminate ambiguity during outages.

Can I generate a runbook that cross-references my system architecture and dependencies?▼

Yes, you can generate a runbook that cross-references your system architecture and dependencies, ensuring the incident response procedures reflect the current design and operational constraints of your infrastructure.

How do I maintain runbooks after resolving an incident to keep them updated?▼

To maintain runbooks after an incident, follow the generated post-resolution steps and maintenance sections to update procedures, ensuring documentation stays aligned with current system architecture and operational requirements.