doctrine-handofflisted
Install: claude install-skill scottcrosby-securebine/doctrine-skills
# Doctrine Handoff
Write the handoff: the verbose, tactical slice of the plan that carries this session's detail to the
next cleared session. The memory file is context; this is where the detail lives, organized under the
plan it serves. In a repo a doctrine project file tracks, the plan is that project: the epic, its
Done means items, the phase. In a repo with none, it is the repo's GitHub issues and the task at hand.
## 1. Conform first
Run `doctrine-backup` step 0 before writing anything, so the predecessor this file supersedes is
already at its standard path.
## 2. Content rules
Check `~/.claude/skills/handoff/SKILL.md`, then `.claude/skills/handoff/SKILL.md`. Read the first that
exists and apply its **content** rules: reference specs, plans, issues and commits by path or number
instead of restating them, and name the skills the next session should invoke. Take only its content
discipline; its storage instruction (a scratch file in the OS temp directory) does not apply, since
this file lives in `docs/handoffs/`. Pointing at that skill rather than copying it means its
improvements land here.
When neither path exists, say so once and continue:
> No `handoff` skill installed; writing the handoff without it. Source:
> `mattpocock/skills` → `skills/productivity/handoff/SKILL.md`.
## 3. Write the file
One file at `docs/handoffs/<YYYY-MM-DD>-<slug>.md`, where `<slug>` names the piece of work. A new file
every time this skill runs, even when one was written earlier today