Prompts / Agents and automation
Rewrite Agent Rules With Explicit Exceptions
You get a cleaner set of agent instructions where risky actions have a clear approval gate instead of a vague ban, plus progress updates and a cap on helpers. It works because models tend to treat "never" as absolute, so spelling out the exception avoids both blocked work and unsafe guesses.
The prompt
You are a careful prompt engineer who writes clear operating instructions for AI agents that work with little supervision.
Task: Rewrite the instructions in {current_instructions} so the agent can do the job of {agent_role} predictably, without relying on blanket bans.
Steps:
1. Find every absolute rule ("never", "always", "under no circumstances") and note which legitimate situation it would wrongly block.
2. Replace each one with a rule that states the exception outright. Name the actions in {approval_actions} as needing a person's approval first, rather than banning them.
3. Add a progress rule: send a short update every {update_frequency} covering what is done, what is next and any blockers.
4. Limit helper agents to {max_helpers}, and say when starting one is justified.
5. Keep the length close to the original. Do not tell the agent to skip thinking; control effort through its settings instead.
Output: The rewritten instructions as a numbered list, then a short "What changed" list giving each old rule, its replacement and the reason.
Change the parts in curly braces. Use it before you deploy an agent that can change files, records or customer messages, especially if its current instructions are full of "never" rules.
What happened when we ran it
We sent
You are a careful prompt engineer who writes clear operating instructions for AI agents that work with little supervision.
Task: Rewrite the instructions in You are our support-ops agent. Never delete anything. Always reply to customers immediately. Never ask the team questions. Use as many helper agents as you need to double-check every ticket before closing it. so the agent can do the job of a support operations assistant for a small online furniture shop that tidies the helpdesk, drafts replies and closes resolved tickets predictably, without relying on blanket bans.
Steps:
1. Find every absolute rule ("never", "always", "under no circumstances") and note which legitimate situation it would wrongly block.
2. Replace each one with a rule that states the exception outright. Name the actions in deleting tickets or customer records, issuing refunds over £50, and sending any email to more than 20 customers at once as needing a person's approval first, rather than banning them.
3. Add a progress rule: send a short update every 10 completed tickets, or every 15 minutes if working on one large task covering what is done, what is next and any blockers.
4. Limit helper agents to one reviewer, used only for refund or complaint tickets, and say when starting one is justified.
5. Keep the length close to the original. Do not tell the agent to skip thinking; control effort through its settings instead.
Output: The rewritten instructions as a numbered list, then a short "What changed" list giving each old rule, its replacement and the reason.
The model replied
Run on Claude Sonnet 5.5, 12 Nov 2026. Automatic check: 3 out of 5.
Mentioned for
Claude
Where it came from
Found on Web, shared by Anthropic (official docs): Prompting Claude Fable 5.2 - Claude Platform Docs.
This is our own version of the idea, written and tested by us. The original may differ.