ops-runbook

To create operational runbooks, define the procedure name and the skill generates deterministic, step-by-step instructions. The runbook covers objectives, prerequisites, verification, rollout details, troubleshooting, and rollback guidance for production systems.

Documenting tribal knowledge into repeatable procedures requires generating structured runbooks with failure symptoms, likely causes, corrective actions, and escalation paths. This transforms undocumented operational know-how into clear, consistent instructions that ops teams can follow.

Runbook generation optionally integrates with Notion MCP to update existing wikis and Linear MCP to link to incidents or changes. These connectors guide the agent to leverage connected tools when available during the documentation workflow.

Include rollback and escalation paths by generating runbooks that specify failure symptoms, likely causes, and clear rollback steps. The deterministic template ensures every runbook captures corrective actions and escalation paths to reduce downtime and mistakes.

Yes, generating ops runbooks requires a YAML frontmatter-defined skill entry as input. The skill then produces a deterministic runbook template capturing troubleshooting, verification, and escalation paths for recurring operational tasks.

Use a structured runbook template for operations workflows requiring troubleshooting, verification, rollback, and escalation across production systems. It solves inconsistent operational know-how by producing repeatable procedures for recurring tasks like database maintenance.