danielrosehill/Claude-Backup-Planner-Plugin

save-backup-infra

Capture the user's available backup infrastructure (S3/B2/R2 buckets, rsync.net, NAS, external drives, existing restic repos, etc.) to persistent memory so it can be reused across projects without re-asking. Use when the user mentions backup destinations, or…

Quellsprache: Englisch

document-backup-strategy

Write the authoritative backup strategy document for the project — the approved option from evaluation, spelled out with schedules, retention, responsibilities, and monitoring. Use after the user has approved an option.

Quellsprache: Englisch

evaluate-backup-options

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.

Quellsprache: Englisch

generate-backup-scripts

Generate the actual backup scripts and scheduling units (systemd timers, cron, GitHub Actions, Kubernetes CronJobs) that implement the documented strategy. Use after BACKUP-STRATEGY.md is approved.

Quellsprache: Englisch

identify-data-to-protect

Inventory the data assets that need backup protection — databases, volumes, user uploads, configs, secrets — and assign each a criticality tier, RPO, and RTO. Use after the deployment architecture is mapped.

Quellsprache: Englisch

identify-deployment-arch

Analyze the current project to identify deployment architecture — where code runs, what services it depends on, where state lives. Use at the start of a backup-planning engagement, before deciding what to protect.

Quellsprache: Englisch

restore-plan

Document and rehearse the restore procedure — the other half of a backup that most plans skip. Produces a runbook and a testing schedule. Use after scripts are generated, and whenever a drill is due.

Quellsprache: Englisch