From ccds-infra
Disaster recovery, backup strategy, RPO / RTO targets, cross-region failover, and restore drills. Auto-invoked when designing DR posture, reviewing backup coverage, or running recovery game-days.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ccds-infra:infra-dr-backupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
"We have backups" is not a DR posture. Untested backups are Schrödinger's
"We have backups" is not a DR posture. Untested backups are Schrödinger's backups — they exist and don't exist until you try to restore. What counts is restore time under pressure, with evidence.
| Tier | RPO | RTO | Topology | Drill cadence |
|---|---|---|---|---|
| T0 (revenue/safety critical) | ≤ 5 min (PITR / continuous) | ≤ 1 h | warm-standby or active-active | quarterly, full failover |
| T1 (important, degradable) | ≤ 1 h | ≤ 4 h | pilot-light | semi-annual, partial restore |
| T2 (best-effort) | ≤ 24 h | ≤ 72 h | backup-and-restore | annual, tabletop + sample restore |
Topology cost rises steeply left-to-right (active-active ≈ 2× run cost; backup-and-restore ≈ storage only) — tie each tier choice to the dollar cost of the outage hour it prevents, and record it as an ADR.
Related: infra-sre (SLO impact of RPO/RTO, incident practice), infra-k8s
(Velero / PV snapshots), infra-finops (standby + storage cost) · domain agent:
infra-architect · output/ADR format: playbook-conventions
npx claudepluginhub ggrace519/claude-code-dev-studio --plugin ccds-infraProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.