Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.
Installs into .claude/skills of the current project.
Are you the author of Runbook?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/suboss87-runbook)
---
name: runbook
description: Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.
---
# runbook
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
## Purpose
An operating runbook with recovery steps and ownership.
Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/runbook.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
## Principles
- Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
