ops-runbook

Generates operational runbooks covering daily procedures, maintenance, and troubleshooting for production systems.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill ops-runbook-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-runbook
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/operations/ops-runbook
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill ops-runbook-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operations teams need consistent, signed-off documentation for running production systems, but writing runbooks manually is slow and often skipped. This Skill generates a complete operations runbook from infrastructure and deployment specifications, gated by human signature approval. ## Core Features & Use Cases - Runbook Generation: Produces a structured Markdown runbook covering daily checklists, health checks, common procedures, troubleshooting guides, and maintenance windows. - Governance & Validation: Enforces nine validation rules including signed prerequisites, canonical output paths, placeholder detection, and approval tables before sign-off. - Traceability: Writes a sources file recording predecessor documents, question history, and information gaps for every generation. - Use Case: After infrastructure and deployment documents are signed in Phase 11, an operations lead invokes this Skill to produce the Phase 12 operations runbook consumed by incident templates and closure reports. ## Quick Start Ask the agent to create the operations runbook for your project once the deployment runbook and infrastructure spec are signed.

Frequently Asked Questions about ops-runbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an operations runbook for a production system?▼

Invoke the ops-runbook skill after the deployment-runbook and infra-spec documents are signed. It gathers application name, team contacts, SLAs, and key components, then generates a runbook with daily checklists, procedures, and troubleshooting guides.

What should an operations runbook include?▼

A runbook should include system overview, team and escalation contacts, daily checklists, common procedures like restarts and scaling, troubleshooting guides for errors and performance issues, maintenance windows, and security operations.

What documents must be signed before generating an operations runbook?▼

The deployment-runbook and infra-spec documents from Phase 11 Infrastructure must exist and be signed. The skill blocks generation and reports which prerequisite is missing if either is unsigned.

Who approves an operations runbook before it takes effect?▼

The Operations Lead holds final approval authority over the runbook. The Engineering Lead and Security Lead are required reviewers, while the DevOps Lead and Technical Lead provide non-gating content reviews.

Why does runbook generation fail with a blocked prerequisite error?▼

Generation fails when a prerequisite skill's document is not signed yet, when the output is not at its canonical path, or when placeholder text remains. Each validation failure returns a specific message identifying the blocking rule.