From 8bd9d7bf0115226b1e300a50de4820a102e1308f Mon Sep 17 00:00:00 2001 From: Amolith Date: Fri, 26 Dec 2025 11:22:03 -0700 Subject: [PATCH] docs(agents): fix task status field values Assisted-by: Claude Opus 4.5 via Crush --- dot_config/AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dot_config/AGENTS.md b/dot_config/AGENTS.md index 91f21e84460da1ffae436be07e3ef9ab679cee64..e62b2049350da1c5968319d7a5427c8ecc69305c 100644 --- a/dot_config/AGENTS.md +++ b/dot_config/AGENTS.md @@ -84,7 +84,7 @@ Resources accept UUIDs or `lunatask://` deeplinks as IDs, config keys for areas/ #### task formatting -Use `[title](lunatask://...)` syntax when including deep links. 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`. +Use `[title](lunatask://...)` syntax when including deep links. 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 status `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.