Zakaria/open-design
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
a46764fb1b
open-design/skills/eng-runbook/SKILL.md
Zakaria a46764fb1b
Some checks failed
ci / Validate workspace (push) Has been cancelled
Details
landing-page-ci / Validate landing page (push) Has been cancelled
Details
landing-page-deploy / Deploy landing page (push) Has been cancelled
Details
github-metrics / Generate repository metrics SVG (push) Has been cancelled
Details
first-commit
2026-05-04 14:58:14 -04:00

1.5 KiB
Raw Blame History

name description triggers od
eng-runbook 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 "运维手册".
runbook
ops doc
on-call
sre doc
service runbook
运维手册
mode platform scenario preview design_system example_prompt
prototype desktop engineering
type entry
html index.html
requires sections
true
color
typography
layout
components
Write a runbook for our auth service — alerts, dashboards, common procedures, on-call rotation.

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>