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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backup-planner:document-backup-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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`.
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.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin backup-plannerSearches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.