create-runbook

A production runbook for on-call procedures documents step-by-step incident response, verification, rollback, and escalation paths. It ensures operators follow precise, repeatable actions under pressure during service disruptions or routine maintenance.

An operational runbook should include numbered deployment steps, validation checks, rollback guidance, troubleshooting decision trees, and escalation criteria. These structured sections ensure maintenance consistency and provide clear guidance for on-call responders during incidents.

You document rollback procedures and escalation paths by using structured runbook templates. The skill guides you through capturing troubleshooting decision trees and escalation criteria, saving the final validated markdown to your engineering documentation repository.

Yes, you can automatically generate ops documentation for incident management. The skill outputs a validated markdown runbook with consistent naming conventions directly to your engineering docs folder, ensuring repeatable operational procedures across services.

Yes, this runbook generation tool works without external dependencies or components. It uses built-in structured templates and validation checks to produce standalone markdown runbooks for your on-call procedures and maintenance tasks.