create-runbooks

To generate operational runbooks, you define a specified scope and provide deployment evidence, commands, and validation findings. The Skill then produces documentation with exact procedures, verification steps, rollback instructions, and escalation notes in the scope's docs/runbooks directory.

An evidence-based troubleshooting runbook grounds its operational instructions in repository artifacts and verifiable commands. This ensures that procedures, verification steps, and rollback instructions are directly traceable to actual system configurations and scripts.

You document rollback instructions and escalation procedures by providing deployment evidence and validation findings to the runbook generator. It automatically structures these operational details within the generated docs/runbooks directory for the specified scope.

Yes, the runbook generator explicitly warns before destructive operations. It structures operational and troubleshooting procedures to include these warnings alongside verification steps and rollback instructions to ensure safe system management.

To automate runbook creation, you must provide the specified scope, deployment evidence, exact commands, and validation findings. These inputs allow the Skill to generate accurate operational procedures and documentation.

Generated operational runbooks are stored under the specified scope's docs/runbooks directory. This ensures the documentation is organized and accessible within the repository structure.