postgres-backup-recoverylisted

# Outcome Produce a concrete, reviewable result for the workflow below without overstating what was observed, executed, or verified. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Guidance targets PostgreSQL 18; adapt it to deployed versions, tools, providers, tablespaces, extensions, and key systems. The optional Python 3.11 helper renders a local worksheet only and never accesses backups or credentials. ## Use this skill when - A system needs scenario-specific PostgreSQL RPO, RTO, backup, PITR, retention, and restore requirements. - Logical dumps, physical backups, snapshots, replicas, WAL archives, encryption, immutability, or copy locations need an architecture review. - Backup freshness, integrity, dependency chains, credentials, keys, or restore evidence may be inadequate. - Teams need an isolated recovery drill, achieved-RPO/RTO measurement, business validation, and remediation record. ## Do not use this skill when - The task is only replica failover, routing, or availability tuning without backup/recovery scope. - The task is a query, index, schema, or privilege review; use the corresponding PostgreSQL skill. - The task is sequencing an approved production schema/data change; use `postgres-migration-safety`. - The request is to execute a restore or access sensitive backup material without explicit authorization and operational controls. ## Inputs Inspect or obtain: - Systems/data classes, failure scenarios, recovery scope, RPO/RTO, retent