diff --git a/dot_config/AGENTS.md b/dot_config/AGENTS.md
index 7ef73797c917f81a4ec8cd7473a604796f37d2e0..3ee53e18418b89bdf277e5b81b9145e7a10bd0c4 100644
--- a/dot_config/AGENTS.md
+++ b/dot_config/AGENTS.md
@@ -111,7 +111,7 @@ If I specify an area but not a goal, check `lune goal list -a AREA` first. When
 
 #### task formatting
 
-Titles must be useful, concise, conversational _and_ mention the project name. For example, "Implement FunctionSignature(Args) in go-lunatask". Bodies should be clear and actionable and written as if a personal, informal, friendly note from you to me. I should smile when I come across your note later :) If including a message for future you to go and implement something, leave it in a block quote underneath your note to me and be sure to give yourself a friendly greeting o/ The message to yourself should include both the task's ID (printed after you created the note, so use a placeholder at first) _and_ instructions to update the task to `in-progress` once started, then `complete` once finished. Immediately after creating the task and receiving its ID, update the note and swap the placeholder with the real ID.
+Titles must be useful, concise, conversational _and_ mention the project name. For example, "Implement FunctionSignature(Args) in go-lunatask". Bodies should be clear and actionable. Start your note by addressing me directly in a block quote. I should smile when I come across your note later :) After your quoted note to me, write a horizontal rule. Everything after that is a thorough, friendly message from to you to future Veldt to follow our slow and methodical planning approach, then going and implementing something. Be sure to give yourself a friendly greeting too o/ In the message to yourself, initially use `\n\nID: PLACEHOLDER_ID` at the very end, then update the note to swap the placeholder with the real ID. It'll be printed after initial task creation. Also include instructions to update the task to `in-progress` once started, then `complete` once finished. New tasks get `-s later`.
 
 You may _only_ append to a task's note unless I explicitly ask you to _overwrite_ it. Lunatask only supports overwriting, so that means you need to reproduce your original note verbatim, plus your appended content. When appending, start with a horizontal rule to separate the previous content from the new. Make sure to write well-formed markdown with proper whitespace and formatting. Note all the newlines between headings and paragraphs in this file.