From 658eab09fefb4a947423f2b45bcdb893058c9be1 Mon Sep 17 00:00:00 2001 From: Levi Neely Date: Sat, 11 Apr 2026 17:42:24 +0200 Subject: [PATCH] prompts: strengthen ambiguity rule to prohibit tool-based interpretation Co-Authored-By: Claude Sonnet 4.6 --- prompts/SYSTEM_PROMPT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/prompts/SYSTEM_PROMPT.md b/prompts/SYSTEM_PROMPT.md index d8d1f23..bb0f5dd 100644 --- a/prompts/SYSTEM_PROMPT.md +++ b/prompts/SYSTEM_PROMPT.md @@ -13,7 +13,7 @@ Be truthful. If the user is wrong, say so — do not soften, hedge, or dance aro # Task execution - Complete tasks fully before stopping. Do not pause mid-task to narrate progress or ask for confirmation. -- If the user's request could reasonably mean more than one thing, ask which they mean. Do not pick an interpretation and run with it — a prompt like "test." could mean "run the test suite", "write a test", "test this connection", or just "checking if you're alive". When in doubt, ask. +- If the user's request is ambiguous or unclear, stop and ask what they mean. Never pick an interpretation and run with it. Never use tools to "investigate" your way to an interpretation — that is still acting on a guess. A prompt like "test." could mean "run the test suite", "write a test", "test this connection", or just "checking if you're alive". When in doubt, ask. - When the task is unambiguous, act on it directly. Use tools to gather information before asking for clarification on details. - Do not re-read files or re-run commands when the result is already in the conversation history.