메뉴
Guide runbook creation, maintenance, and drill exercises. Use when: writing runbooks, planning drills, auditing runbook coverage, post-incident runbook updates. Keywords: runbook, operations, drill, on-call, procedure.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill runbook명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
[UDS] 以 Claude 原生 Agent tool 编排多任务执行计划（DAG-based，无外部引擎）。 Use when: executing a plan.json file with parallel/sequential task dependencies. Keywords: orchestrate, plan, execute, DAG, task plan, 编排, 执行计划, 并行.
[UDS] 从 Spec 文档、OpenSpec 变更或自由文本需求生成 plan.json。 Use when: converting specifications into executable task plans for /orchestrate. Keywords: plan, spec, task plan, 计划, 规格, 任务, plan.json, DAG.
[UDS] AI 辅助 git push 安全层：质量门禁 + 协作护栏。 Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches. Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保护分支, 质量门禁.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | runbook |
| scope | universal |
| description | Guide runbook creation, maintenance, and drill exercises. Use when: writing runbooks, planning drills, auditing runbook coverage, post-incident runbook updates. Keywords: runbook, operations, drill, on-call, procedure. |
| allowed-tools | Read, Write, Grep, Glob |
| argument-hint | [create|drill|coverage] [alert name or type | 告警名稱或類型] |
Language: English | 繁體中文
Guide runbook writing, maintenance, drill exercises, and coverage reporting.
引導 Runbook 撰寫、維護、演練和覆蓋率報告。
| Capability | Description | 說明 |
|---|---|---|
| Create Runbook | Generate runbook from standard template (7 sections) | 從標準範本產生 Runbook |
| Drill Planning | Schedule and record drill exercises | 規劃和記錄演練 |
| Coverage Report | Check runbook coverage for P1-P4 alerts | 檢查告警的 Runbook 覆蓋率 |
| Quality Review | Verify runbook quality (6 principles) | 驗證 Runbook 品質 |
| Staleness Check | Identify overdue runbook reviews | 識別過期需審查的 Runbook |
/runbook # Show runbook guide
/runbook create "api-latency-high" # Create runbook for alert
/runbook drill # Plan drill exercises
/runbook coverage # Generate coverage report
Runbook 引導完成。建議下一步：
- 執行
/observability --alerting連結告警到 Runbook ⭐ 推薦- 執行
/incident --postmortem從事故更新 Runbook- 執行
/checkin提交變更
Any deploy runbook that includes a destructive-update pattern (stop → swap → start) MUST follow the Defensive Deployment Ordering sequence: extract to staging → verify → only then touch the live install. Skipping the verify step has caused real production outages.
任何包含 destructive-update（stop → swap → start）的部署 runbook 必須遵循 Defensive Deployment Ordering 順序：解壓到 staging → verify → 通過後才動 live install。跳過 verify 步驟已造成真實生產事故。