When should you use it?
- Your assistant has been running for months and sometimes answers from an older version of your plans
- You have changed prices, suppliers or policies and are not sure every bot picked up the change
- You want one dated record of business decisions that every bot checks first
Not for: Brand-new assistants with little or nothing saved yet; Regulated records that must be kept unchanged for a set period; check retention rules before deleting anything; Assistants that cannot list or edit what they have saved
What do you need, and what do you get?
You need
- An assistant with saved notes or memory you can review, such as Grok Bot
- A shared page or file where a decisions log can live
- Twenty minutes for the first review, then a few minutes each Monday
You get
- Per-topic lists of proposed merges and removals, waiting for your yes
- A shortlist of rules and decisions that should move from loose notes into a page or file
- A dated decisions page updated every week
- A Monday tidy-up report with proposed changes only
How does it work, step by step?
- Count what is savedAsk your assistant how many notes it currently holds. The number tells you how big the first pass will be.
- Paste the promptGive it Fenech's prompt and let it start the first review one subject at a time.
- Approve changes in small batchesRead each proposed merge or removal list and answer yes, no or edit. Nothing should change before your answer.
- Move exact-wording rulesAccept the suggestions to move vetoes, standing decisions and policies into a page or file your bots can check.
- Check the Monday reportEach week, skim the proposed changes and the new decisions entries, and correct anything recorded wrongly.
The prompt
The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, Claude, ChatGPT and others. Values in lime are placeholders.
Original prompt by Michael Fenech (@Michael_Fenech_)
Set up a memory improvement process for me. 1 - Work through my existing notes topic by topic. Find notes that are stale, duplicated or contradict each other. Give me a short list of proposed deletes and merges per topic. Change nothing until I say yes. 2 - Identify notes where the exact wording matters, such as standing decisions, rules and veto lists. Recommend which should become a file or Page instead of a note, and why. 3 - From now on, save rules, not stories. When I make a decision or give a standing instruction, save it as one clear sentence with the date. If it replaces an older note, delete the old one in the same step. 4 - When I say "remember this", save it straight away and confirm in one line. 5 - Keep a Decisions log Page. Each week, add what I decided, with the date, the topic and a link to where it happened. 6 - Every Monday, run a tidy-up and send me proposed deletes and merges. Same rule: change nothing until I say yes. 7 - Before answering anything about the past, check the notes and the Decisions log first, then the chat history. Tell me if you're unsure rather than guessing.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: a prompt to clean up a Grok Bot team's memory and keep a decisions log.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Review what you have saved about {business_name}, one subject at a time. For each subject, list entries that look outdated, repeated or in conflict, and propose merges or removals. Do not change anything until I approve. Suggest which standing decisions and vetoes should move into {decisions_page}, each as one dated sentence. Every Monday, send me proposed changes only, and check {decisions_page} before you answer questions about past decisions.
What can go wrong?
- Approving a whole list at once. Read the proposed removals; an old note can still hold the only copy of a detail you need.
- Letting the decisions page drift. If entries stop carrying a date and a link to where the call was made, it becomes another pile of notes.
- Saving stories instead of rules. A long account of a meeting is harder for a bot to apply than one clear dated sentence.
- Assuming every bot shares one memory. Check how your platform stores notes; some keep separate memory per assistant.
Our take
Memory is one of the most useful features in personal and team assistants, and also one of the easiest to neglect. Fenech's post makes the risk concrete: when a bot holds well over a thousand notes, some will be out of date and a few will contradict each other, and the bot may answer from the wrong one without anyone noticing. What we like about his prompt is that it treats memory like any other business record. It reviews subject by subject, proposes removals rather than making them, and separates rules that need exact wording into a page or file. The habit of saving one dated sentence per decision, and replacing the older note in the same step, is the part most teams will benefit from first. The decisions page also gives people a quick way to see what was agreed and when. The weak spot is approval fatigue: if the lists get long, it is tempting to say yes to everything, so keep batches small. In our dry run on a fictional notes export for a small cleaning company, it grouped 40 notes into five subjects, found three conflicts and two outdated prices, proposed four removals and waited for approval.
Where the time goes back: Correcting an assistant that answers from last quarter's prices or a supplier you already dropped costs time and can cost money. A short weekly review with approval gates keeps saved context current without a big cleanup every few months.
FAQ
Will it delete anything on its own?
Does this need Grok Bot?
Why move some notes into a page or file?
Source and credit
The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X post: a prompt to clean up a Grok Bot team's memory and keep a decisions log
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Nov 17, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Grok Bot
- AI dry run
- Nov 18, 2026: passed. Dry-run tested by our AI test agent on sample input. Stale and conflicting notes surfaced per subject, approval gate held, decisions recorded as dated sentences; no live memory touched.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 18, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.