runbook-writer

name	runbook-writer
description	Create operational runbooks from tribal knowledge, commands, logs, and recovery steps. Use when recurring incidents lack clean response docs.

Runbook Writer

Overview

Create operational runbooks from tribal knowledge, commands, logs, and recovery steps.

Core Workflow

1. Gather the source material, existing conventions, templates, and destination format before drafting.
2. Extract the information that matters most for the intended audience and discard low-signal noise.
3. Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline.
4. Draft the artifact, then surface any missing facts or decisions that still need human input.

Deliver

• A ready-to-edit draft in the expected structure and tone.
• The main sections, decisions, or states the artifact should include.
• Open questions or missing facts that would improve the final output.

Guardrails

• Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs.
• Prefer existing repo or team conventions over generic formatting.
• Keep the output useful and specific rather than padded.
• Do not deploy, apply, rotate, or mutate live infrastructure unless the user explicitly asks for it.