takenoteslisted

# /takenotes — Harvest a session into durable memory Write this session's durable knowledge somewhere it survives a `/clear`. This is **not** a transcript dump. It is a harvest, a reconcile, and a routing decision. The value of this skill over a plain "save that to memory" is **Step 3**. Anyone can append a new fact. Almost nobody goes back and checks whether what's already stored is still true. Do not skip it. --- ## Step 0 — Scope gate (always first) Decide which of these you're doing. Getting this wrong makes the skill annoying to use. | Situation | Do this | |---|---| | One discrete fact ("remember I prefer tabs", "the API key rotates monthly") | Take the **single-fact path** below. Do not run Steps 2–5. | | Session checkpoint — solved a problem, made a decision, finished a feature, asked to "save what we learned" | Full harvest. Continue to Step 1. | | A topic argument was passed (`/takenotes auth flow`) | Full harvest, but scope Steps 2–4 to that topic only. | | Called from `/putdown` | Full harvest. Continue to Step 1. | | Nothing durable happened (pure Q&A, reading code, no decisions) | Say so plainly in one line and stop. Do not manufacture findings to look productive. | ### Single-fact path Skipping Steps 2–5 must not mean skipping the rules for writing a memory correctly. Do all of these, then stop: 1. **Locate the memory directory** (Step 1a) — you still need to know where to write. 2. **Check for an existing memory on the topic** (`ls "$MEMDIR/memory/"`