DR/BCP planning — RPO/RTO definition, failover design, backup strategies, tabletop exercises. Use when the user asks to "plan disaster recovery", "define RPO/RTO", "design failover", "create BCP", or mentions business continuity, backup strategy, recovery runbook, tabletop exercise.
Disaster recovery planning ensures organizational resilience through defined recovery objectives, failover designs, and tested recovery procedures. The skill produces DR plans, recovery runbooks, and test schedules that minimize downtime and data loss during disruptive events.
The user provides a system or organization context as $ARGUMENTS. Parse $1 as the system/organization name.
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40%) | tecnica (full, default){TIER}: mission-critical | business-critical | business-operational | all (default)graph TD
subgraph Core["Disaster Recovery"]
A[DR Plan] --> B[RPO/RTO Matrix]
A --> C[Failover Strategy]
A --> D[Recovery Runbooks]
end
subgraph Inputs["Inputs"]
E[System/Org Context] --> A
F[Business Impact Analysis] --> B
G[Criticality Tiers] --> C
end
subgraph Outputs["Outputs"]
A --> H[Plan de DR]
D --> I[Runbooks de Recuperacion]
A --> J[Calendario de Pruebas]
F --> K[Analisis BIA]
end
subgraph Related["Related Skills"]
L[cloud-architecture] -.-> C
M[security-architecture] -.-> D
N[sla-design] -.-> B
end
ops_dr-plan_{organizacion}_{WIP}.mdops_dr-plan_{organizacion}_{WIP}.docxops_dr-plan_{organizacion}_{WIP}.html{fase}_{entregable}_{cliente}_{WIP}.xlsx{fase}_{entregable}_{cliente}_{WIP}.pptx| Dimension | Peso | Criterio |
|---|---|---|
| Trigger Accuracy | 10% | Activa ante "disaster recovery", "BCP", "RPO/RTO", "failover" sin confundir con backup operacional o incident management |
| Completeness | 25% | Cubre BIA, RPO/RTO, failover, runbooks, comunicacion de crisis y calendario de pruebas |
| Clarity | 20% | Runbooks son paso-a-paso ejecutables por operaciones sin interpretacion |
| Robustness | 20% | Maneja legacy sin APIs, restricciones de residencia y presupuesto limitado |
| Efficiency | 10% | 8 pasos donde BIA alimenta todo lo demas; sin pasos redundantes |
| Value Density | 15% | Runbooks y calendario de pruebas son directamente operacionalizables |
Umbral minimo: 7/10 en cada dimension para considerar el skill production-ready.
Autor: Javier Montaño · Comunidad MetodologIA | Version: 1.0.0