From backup-planner
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.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin backup-plannerThis skill uses the workspace's default tool permissions.
Produce the living document that every future "how do we back this up" question refers back to. Written once the user has picked an option from `03-options.md`.
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.
Produce the living document that every future "how do we back this up" question refers back to. Written once the user has picked an option from 03-options.md.
Write to backup-plan/BACKUP-STRATEGY.md (capitalised so it's visible). Include:
--keep-daily 7 --keep-weekly 4 --keep-monthly 12 --keep-yearly 5). Align with compliance requirements.restore-plan skill). Untested backups are not backups.02-data-inventory.md is either covered or listed as out-of-scope with justification.After writing, append a pointer to the main project README.md under a "Backups" heading so future contributors find it.