claws-rememberlisted

## What this is Engine-internal skill that writes or overwrites a memory file via `mcp__claws__claws_remember`. Auto-invoked after non-obvious wave outcomes; not user-typed. See [[claws-memory-engine]] for the full integration contract and [[claws-recall]] for the required dedup check before every write. ## When to invoke - `/claws-auto` completes a wave with a non-obvious outcome — new failure mode or design constraint not in any existing memory. - `/claws-fix` resolves a novel failure mode not yet in the memory corpus. Document failure signature, fix steps, and runbook_id in a new `feedback` memory. - The user explicitly says "remember that…" or "save this as a memory." ## When NOT to invoke - On every `/claws-do` or `/claws-plan` run — those flows are read-only with respect to memory. - For known failure modes already covered by an existing memory. - When `CLAWS_NO_MEMORY=1` is set — skip silently. ## Steps 1. **Dedup check**: call `claws_recall(query: "<slug or key phrase>", topK: 3)`. If a match exists, overwrite rather than create a duplicate. 2. **Call tool**: `mcp__claws__claws_remember` with `name` (slug), `type`, `description` (≤150 chars), and `body`. 3. **Body structure** for `feedback`/`project`: first line is the rule, then `**Why:**` and `**How to apply:**`. Use ISO dates for all dates in `project` memories. 4. **On `confirm_required`**: ask user to confirm; retry with `confirmed: true`. 5. **Post-write**: log `[memory] Saved: [<type>] <slug>` in PROGRES