From backup-planner
Recommend the best-fit backup strategy for the project given its data inventory and the user's available infrastructure. Produces a ranked options brief with trade-offs. Use after architecture and inventory are mapped.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin backup-plannerThis skill uses the workspace's default tool permissions.
Synthesize the data inventory and the available infrastructure into 2–3 concrete strategy options, with a clear recommendation.
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Share bugs, ideas, or general feedback.
Synthesize the data inventory and the available infrastructure into 2–3 concrete strategy options, with a clear recommendation.
backup-plan/01-architecture.mdbackup-plan/02-data-inventory.mdreference_backup_* memory files (see save-backup-infra)If any are missing, run the corresponding upstream skill first.
For each candidate strategy, score against:
pg_dump / pg_dumpall for logical, pg_basebackup + WAL for PITR, or managed provider snapshotsmysqldump, mariabackup, or managed snapshotsVACUUM INTO or file copy with WAL checkpointmongodump, or Ops ManagerWrite to backup-plan/03-options.md:
# Backup Strategy Options
## Option A — <name>
- Tooling: ...
- Destinations: ...
- RPO/RTO delivered: ...
- 3-2-1 status: ...
- Monthly cost estimate: ...
- Pros / Cons
## Option B — ...
## Recommendation
<which option, why, what open questions remain>
End with an explicit ask to the user to approve one option before moving to document-backup-strategy.