document-runbook

A deployment runbook documents the step-by-step process for deploying applications across environments. This Skill generates structured runbooks with copy-paste-ready commands, pre-flight checklists, and rollback procedures saved as markdown files in /docs/runbooks/, standardizing deployment workflows across your team.

Runbooks should document deployment steps, failure scenarios with recovery procedures, rollback options, troubleshooting sections, and pre-flight checklists. This Skill enforces a consistent template structure that makes runbooks easy to follow and audit for CI/CD, rollout, migration, and incident response scenarios.

Yes. This Skill applies MADR-like structure to enforce consistency across runbooks. It generates ready-to-use markdown templates with actual executable commands, failure steps, and recovery procedures, ensuring every team member follows the same standardized deployment process across environments.

Runbooks document explicit rollback steps and recovery procedures for failures, reducing incident response time and human error. This Skill includes failure scenarios and rollback options in each runbook, enabling teams to execute recovery procedures confidently during outages or failed deployments.

Runbooks are generated as markdown files organized in /docs/runbooks/[process-name].md, making them version-controllable, searchable, and easy to integrate into documentation systems. The markdown format supports code blocks, checklists, and structured sections for commands and procedures.