mistakelisted

# Record a mistake The entry goes into the **file memory under git**: `${user_config.memory_dir}/mistakes/`. Not into MemPalace: the palace is the index of the notes vault, not a journal. A file can be read, edited, diffed and reverted, which is exactly what a mistakes journal needs. ## This skill only records It decides nothing. The weekly review (`/agent-memory:memory-review`) reads the whole folder, groups entries by substance, moves repeats one step up (a rule, then a hook), writes the analysis into `${user_config.memory_dir}/scripts/consolidation-log.md` and empties the folder. Hence: - **Do not look for duplicates.** Grouping needs the whole folder at once; a session sees only its own mistake. - **Do not propose a rule or a hook.** The step is set from the whole picture: once is noise, twice is a rule, three times is a hook. That count is invisible from inside one session. - **Write freely and in detail.** It is a draft, and nothing is lost: the folder is under git. One exception: the user said to create a rule or hook. Then it is their decision, and it is done as an ordinary task, not inside this skill. ## Steps **1. Write the entry: four lines, in English** (the user's verbatim words stay in quotes as they are). ``` MISTAKE: [what I did wrong] WHY: [what caused it] FIX: [how it was fixed now] PATTERN: [how not to repeat it: the valuable part] KIND: mistake | dead_end ``` `KIND: dead_end` is for an approach that was tried and does not work here (a flag tha