Stats
Actions
Tags
From backup-planner
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backup-planner:identify-data-to-protectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn the architecture map into a concrete protection inventory. Every item gets a tier, a target RPO (how much data loss is acceptable), and a target RTO (how fast recovery must complete).
Turn the architecture map into a concrete protection inventory. Every item gets a tier, a target RPO (how much data loss is acceptable), and a target RTO (how fast recovery must complete).
backup-plan/01-architecture.md if it exists. If not, run identify-deployment-arch first.critical (business-ending loss), important (painful loss), nice-to-have (re-creatable with effort)Write to backup-plan/02-data-inventory.md:
# Data Protection Inventory
## Critical
- <asset> — <size>, RPO <x>, RTO <y>, <notes>
## Important
- ...
## Nice-to-have
- ...
## Excluded (and why)
- ...
## Restore Prerequisites
- <secrets, DNS, account config that must exist for a restore to succeed>
This document drives evaluate-backup-options.
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.