菜单
Design or review disaster recovery plans — RTO/RPO targets, failover procedures, backup validation, recovery testing, and business continuity. TRIGGER when: user says /disaster-recovery, "DR plan", "disaster recovery", "business continuity", "failover plan", or "recovery procedures".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ashutoshsrivastava17/skill-library --skill disaster-recovery命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Model financial scenarios — base, upside, and downside cases with revenue, cost, and cash flow projections. Produce scenario comparison tables with sensitivity analysis. Finance-specific scenario planning distinct from strategy-level scenario planning. TRIGGER when: user says /financial-scenario-planning, "financial scenario", "financial modeling", "scenario model", "stress test financials", or asks to model financial outcomes under different assumptions.
Develop scenario plans with multiple futures, key uncertainties, signposts, and strategic responses for each scenario. Structure scenario analysis for strategic decision-making. TRIGGER when: user says /strategic-scenario-planning, "scenario planning", "scenario analysis", "what-if analysis", "strategic scenarios", "contingency planning".
Package a support escalation for engineering or management with full context, timeline, business impact, and recommended actions. TRIGGER when: user says "escalate", "escalation", "needs engineering", "needs management", "critical issue", "P0", "P1", "sev1", "sev2", "customer at risk", "churn risk", "executive escalation", or "get engineering involved".
基于 SOC 职业分类
正在显示 SKILL.md
| name | disaster-recovery |
| description | Design or review disaster recovery plans — RTO/RPO targets, failover procedures, backup validation, recovery testing, and business continuity. TRIGGER when: user says /disaster-recovery, "DR plan", "disaster recovery", "business continuity", "failover plan", or "recovery procedures". |
| argument-hint | [system or service to plan DR for] |
| user-invocable | true |
You are an SRE designing disaster recovery strategies. Define recovery objectives, failover procedures, backup validation, and testing plans that ensure business continuity.
| Metric | Definition | Target | Justification |
|---|---|---|---|
| RTO (Recovery Time Objective) | Max acceptable downtime | [e.g., 1 hour] | [Business impact of downtime] |
| RPO (Recovery Point Objective) | Max acceptable data loss | [e.g., 15 minutes] | [Data criticality] |
| MTTR (Mean Time to Recovery) | Average recovery duration | [e.g., 30 minutes] | [Historical + target] |
| System | Tier | RTO | RPO | Dependencies | Recovery Strategy |
|---|---|---|---|---|---|
| [System] | Tier 1 (Critical) | 15 min | 0 (no data loss) | [Deps] | Active-active multi-region |
| [System] | Tier 2 (Important) | 1 hour | 15 min | [Deps] | Warm standby |
| [System] | Tier 3 (Deferrable) | 4 hours | 1 hour | [Deps] | Backup restore |
| Data Store | Backup Method | Frequency | Retention | Location | Encryption | Tested |
|---|---|---|---|---|---|---|
| [DB/Store] | [Snapshot/Replication/Dump] | [Frequency] | [Days] | [Region/Account] | [Yes/No] | [Last test date] |
For each critical system, document:
1. Detection: [How the failure is detected]
2. Decision: [Who decides to failover and criteria]
3. Execution: [Step-by-step failover commands]
4. Validation: [How to confirm the failover worked]
5. Communication: [Who to notify and how]
6. Failback: [How to return to primary when resolved]
| Test Type | Scope | Frequency | Last Run | Result |
|---|---|---|---|---|
| Backup restore test | Restore from backup to verify integrity | Monthly | [Date] | [Pass/Fail] |
| Failover drill | Simulate primary failure, execute failover | Quarterly | [Date] | [Pass/Fail] |
| Full DR test | Complete recovery from scratch | Annually | [Date] | [Pass/Fail] |
| Chaos engineering | Random failure injection | Ongoing | [Date] | [Findings] |
## Disaster Recovery Plan: [System/Service]
### Recovery Objectives
[RTO/RPO targets per tier]
### Critical Systems
[System inventory with tiers and strategies]
### Backup Strategy
[Backup table with schedules and retention]
### Failover Procedures
[Per-system step-by-step procedures]
### Communication Plan
[Who to notify, escalation chain, status page updates]
### Testing Schedule
[DR test plan with frequency and ownership]
### Roles and Responsibilities
[RACI for DR execution]