Assisted-by: Claude Opus 4.7 via Claude Code

diff --git a/AGENTS.md b/AGENTS.md
index 0f3a042..b7374a5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -6,6 +6,8 @@ The backlog lives in the `ranger` CLI, not GitHub Issues. Use `ranger` to read a
 
 The backlog shifts between sessions and even within a session — tasks get reordered, retitled, moved between states, closed, or added by the user without notice. Before acting on a task you remember (or one referenced earlier in the conversation), re-run `ranger task show <key>` and confirm state, ordering, and description against ground truth. Do not trust earlier `ranger task list` output to still be accurate; refetch when placement matters (e.g. moving to top/back of ready).
 
+When the user asks to add a task, the only command you should run is `ranger task create`. Do not run `ranger backlog list`, `ranger task list`, `ranger task show`, or read any code files to "verify" or "scope" the task — write the task from what the user said, verbatim if possible. The default backlog is already set via `RANGER_DEFAULT_BACKLOG`, so `--backlog` is unnecessary. Investigate only if the user asks you to pick up the task.
+
 ## Before committing
 
 Always run `just all` and verify everything passes before committing. No exceptions — this is not optional. If you commit without running it, you will break the build.