# Engineering Runbook

Writes an on-call runbook with alerts, procedures and an incident response checklist.

- Repository: https://github.com/nexu-io/open-design (105332 stars)
- Category: DevOps
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nexu-io/open-design --skill eng-runbook -g -a claude-code -y`
Codex: `npx skills add nexu-io/open-design --skill eng-runbook -g -a codex -y`
Cursor: `npx skills add nexu-io/open-design --skill eng-runbook -g -a cursor -y`
Gemini CLI: `npx skills add nexu-io/open-design --skill eng-runbook -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add nexu-io/open-design`

## Description

An engineering runbook, service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Engineering Runbook Skill

Produce a single-page engineering runbook.

## Workflow

1. Read DESIGN.md.
2. Identify the service from the brief.
3. Layout:
   - Header: service name, owner team, severity tier, version.
   - Service summary paragraph + dependency list.
   - Alerts table: alert name / severity / what it means / first response.
   - Dashboards & links list.
   - Common procedures block (3, 4) with code blocks (deploy, rollback, rotate keys).
   - On-call rotation table (week / primary / secondary / backup).
   - Incident response checklist (5 numbered steps).
4. One inline `<style>`, semantic HTML, monospace for code blocks.

## Output contract

```
<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>
```