← ClaudeAtlas

doctrine-backuplisted

Use when the user asks to back up the session, save session memory, update SESSION_MEMORY.md, or wrap up so the next session can pick up where this one left off. Writes the repo's memory file as survivable session context and red-teams it before reporting done.
scottcrosby-securebine/doctrine-skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill scottcrosby-securebine/doctrine-skills
# Doctrine Backup Write the session's memory file: survivable context, the color and taste the next session needs beside the handoff. It does not direct the work; the handoff does (`doctrine-handoff`). Works in any repo, with or without a doctrine project file or an open doctrine phase. **Update** the memory file; do not compose it from scratch. Read the existing file first and carry forward everything you cannot disprove. Target ≤400 words. The only edits you make are for correctness: a line the repo, the record or this session shows is wrong. ## 0. Conform the repo The standard is one memory file, `SESSION_MEMORY.md` at the repo root, and every handoff under `docs/handoffs/`. Before anything else, bring a repo that differs to it: - **Ignore first.** In a public repo, or one an installer's tooling copies whole, `docs/handoffs/` is in `.gitignore`; add it when it is not. `gh repo view --json visibility --jq .visibility` answers the first, and when `gh` errors (no remote, not authenticated) treat the repo as public; `.claude-plugin/plugin.json` or `.claude-plugin/marketplace.json` present answers the second. Doing this before any move keeps an untracked handoff from being committed there; a handoff already tracked stays tracked. - **Memory file.** `ls` the root, and keep the current memory file's text as it stands now, before any move or write: step 5 hands it to the red team as the previous file, and a later pass through this step, from step 5 by way of `do