learn-procedure

# /learn-procedure Capture a **repeatable task-execution procedure** from the work just completed in this conversation and persist it as a **memory node** the assistant recalls automatically in future sessions. The pain this solves: multi-step task workflows (e.g. "rename a folder of images to each user's email using the roster .xlsx") get re-derived from scratch every session because nothing durable remembers the steps. A procedure is stored as a normal memory-tree node with `kind: procedure`. It surfaces through the **existing** `UserPromptSubmit` recall hook — no new retrieval path — when a future prompt's intent matches the procedure's `description`. ## Relationship to /learn-this and /preserve (read this — single source of truth) - `/learn-this` → teaches the USER a topic and records what they LEARNED (`$VAULT/Learning/`). - `/preserve` → silently saves preferences/decisions/facts about the user (`$VAULT/CLAUDE.md`). - `/learn-procedure` → saves a HOW-TO the ASSISTANT should re-run: an executable, step-based task workflow (the auto-memory dir's `procedures/` subdir — see step 1). Never duplicate the same content across these. A procedure is steps-to-execute, not a fact about the user and not a lesson for the user. If a procedure relates to a learning record, link with a `see_also` edge — do not copy. ## When to use Invoke after finishing a **multi-step task** that is likely to recur, where re-deriving the steps next time would be wasteful. Do NOT capture one-off...