When should you use it?
- A bot has been running for weeks and you are no longer sure what rules it is following
- Two bots keep doing overlapping work, or work falls between them
- Priorities changed this month and the bot still acts on last month's
Not for: Brand-new bots with no instructions yet; write a first brief instead; Tracing one specific repeated mistake back to a conflicting rule, which needs a narrower audit; Assistants that cannot show or edit their own standing instructions
What do you need, and what do you get?
You need
- One bot whose standing instructions you want to review
- Ten to fifteen quiet minutes, ideally in a voice conversation
- A rough idea of what the bot is judged on and which actions need your approval
You get
- The bot's current instructions, with stale items flagged and explained
- Agreed wording for its goal, ownership, hard limits, current priorities and where detail lives
- A revised instruction set shown to you for approval before it is saved
How does it work, step by step?
- Pick one botStart with the bot you rely on most or the one whose results have drifted.
- Start a voice chatFenech suggests voice, so you can question vague lines as the bot reads them back.
- Paste the promptGive it Fenech's prompt. It shows its instructions and asks about anything that looks out of date.
- Answer one part at a timeWork through goal, ownership, limits, priorities and file locations, correcting wording before moving on.
- Approve the rewriteRead the revised instructions in full before saying yes, and check that the approval rules are explicit.
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_)
Show me your current instructions. Flag anything that looks out of date, explain why and ask me whether it still applies. Then work through these five parts with me. Ask one question at a time. Read each section back so we can get the wording right before moving on. 1. Goal: one sentence on what I'm judged by. 2. What I own and what I don't: who does which job, so I hand work to the right bot. 3. Hard limits: the never-without-your-yes rules, each in one sentence. 4. Priorities right now: your top two or three for this month, in order, so I know what wins when time is short. 5. Where the detail lives: the file and skill names, kept out of the description itself. When we’re done, show me the revised instructions for approval.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: ask your Grok Bot to show its instructions, then rebuild them in five parts.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
List the standing rules you apply to every task for me. Mark any that seem outdated and say why, then check with me before keeping them. Next, help me rewrite them under five headings: {bot_role}'s main goal, the work it owns versus hands off, actions that always need my approval, the top priorities for {period}, and which files hold the details. Take one heading at a time and confirm the wording with me. Show the full rewrite and wait for my OK before saving.
What can go wrong?
- Leaving ownership vague. A line like handles follow-ups should say whether the bot drafts or sends, as Fenech's example shows.
- Stuffing the detail into the instructions. Point to the files and skills instead, so the core stays short and readable.
- Listing too many priorities. Keep it to the top two or three so the bot knows what wins when time runs short.
- Approving without reading. The revised set replaces what came before, so read every hard limit before you confirm.
Our take
Standing instructions are the most important text in any agent setup and the one people look at least, mostly because they are written once and then buried. Fenech's prompt is valuable because it starts by making the bot show its rules and flag the stale ones, which turns an invisible problem into a list you can act on. The five-part structure is sensible: a one-line goal, clear ownership so work goes to the right bot, hard limits that need your yes, a short ranked list of current priorities, and pointers to files rather than pasted detail. We especially like the one-question-at-a-time pace and the read-back before moving on, which stops the bot from rewriting everything in one confident pass. His voice example, asking whether owning follow-ups means drafting or sending, is exactly the kind of gap that causes real trouble. Run it monthly or whenever priorities shift, one bot at a time. In our dry run on a fictional sales assistant's instructions, it flagged a retired add-on, turned a vague follow-up rule into draft-then-approve and moved pricing detail into a file reference.
Where the time goes back: Stale or vague standing instructions cause small wrong turns on every job, and finding them by trial and error takes weeks. A single guided review surfaces them in one sitting and leaves a short, clear set the bot can follow.
FAQ
Why do this by voice?
How is this different from an instruction conflict audit?
Does it only work in Grok Bot?
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: ask your Grok Bot to show its instructions, then rebuild them in five parts
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Nov 16, 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 17, 2026: passed. Dry-run tested by our AI test agent on sample input. Stale rules surfaced, ownership and limits explicit, nothing saved without approval.
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 17, 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.