AsiaOstrich Runbook Assistant | Runbook 助手
Language: English | 繁體中文
Guide runbook writing, maintenance, drill exercises, and coverage reporting.
引導 Runbook 撰寫、維護、演練和覆蓋率報告。
Capabilities | 功能
| 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 |
Usage | 使用方式
/runbook # Show runbook guide
/runbook create "api-latency-high" # Create runbook for alert
/runbook drill # Plan drill exercises
/runbook coverage # Generate coverage report
Next Steps Guidance | 下一步引導
Runbook 引導完成。建議下一步：
- 執行
/observability --alerting連結告警到 Runbook ⭐ 推薦- 執行
/incident --postmortem從事故更新 Runbook- 執行
/checkin提交變更
Deploy Runbook — Mandatory Rule
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 步驟已造成真實生產事故。
Reference | 參考
- Detailed guide: guide.md — runbook creation, organization and validation. Read it when writing runbooks, reviewing operational procedures, planning drills, or assessing coverage.
- Core standard: runbook-standards.md
- Related: alerting-standards.md
- Related: postmortem-standards.md
- Related: deployment-standards.md § Defensive Deployment Ordering — mandatory ordering for destructive deploys
- Related: packaging-standards.md § Archive Format Integrity — upstream pair to defensive ordering