memory-handofflisted

# memory-handoff Coding sessions die with their transcripts. A memory handoff is a short structured note that a memory owner (a long-lived agent, a teammate, or future you) can review and file into durable memory. This skill pairs with [brigade](https://github.com/escoffier-labs/brigade), which lints and ingests handoffs, but works standalone. In a Brigade-wired repo the handoff is the closing gate of the [Brigade process model](../../../docs/brigade-process-model.md). This skill owns the handoff itself: format, quality bar, routing sections, and lint. ## When a handoff is warranted Durable knowledge only: architecture decisions, non-obvious root causes, environment gotchas, workflow changes, security findings, reusable commands or patterns, user preferences, research findings. Not task chatter, not anything the repo already records (code, git history, existing docs). ## Where to write it 1. If the repo has a brigade inbox (check `.brigade/` config) or an existing handoff dir (`.claude/memory-handoffs/`, `.codex/memory-handoffs/`), write there. 2. Otherwise create `.claude/memory-handoffs/` and write there. Filename: `YYYY-MM-DD-HHMM-<slug>.md` ## Format ```md # Memory Handoff ## Type setup | workflow | bugfix | decision | security | preference | research | project-context ## Title Short, specific title ## Summary 2 to 4 sentences. What happened and why it matters. ## Durable facts - Fact 1 - Fact 2 ## Evidence - files changed: ... - commands run: ... - error st