notebooklisted

# Claude Notebook Save the current Claude Code session as a per-session note at `03.13 Agent notebook/YYYY-MM/Agent session YYYY-MM-DDTHHMM.md`. **One file per session, grouped by month** in a `YYYY-MM/` subfolder. Session metadata (id, model, scope, tags) lives in YAML frontmatter; the body is just the H1 (matching `title`) plus free-form prose. See [[03.05 Conventions & policies for category 03#Engineering notebook—one file per session]] in the vault for the canonical convention. ## What to do ### 1. Synthesize the entry - **Headline** (≤10 words) — the main thing accomplished. Becomes the H1 (and `title`). - **Body** — first person, honest, concise; write for future-you. Cover: - What was the goal - What shipped (concrete artifacts, files, PRs, commits) - What broke and what you learned - Key decisions made - **Open questions** — forks in the road, design calls deferred - **Loose ends** — small atoms that need 30 seconds next time - **Topic tags** — 3–7 relevant tags. Go in the `tags:` frontmatter array alongside `llm/agent`. ### 2. Identify touched scopes List every area / category / project the session worked on. These go in `session-scope:` as a YAML list of wikilink strings. Backlinks from each scope's landing note will surface this session. Examples: - System-meta work (JD conventions, `00.x` notes) → `"[[00 System management]]"` - Claude Code tooling (plugins, prompts, configs) → `"[[03 LLMs & agents]]"` - Specific projects → `"[[92005 jd-tools]]"