From 2e889e54a6420ba1748510ead26b4de0e1371523 Mon Sep 17 00:00:00 2001 From: Amolith Date: Mon, 22 Dec 2025 18:27:21 -0700 Subject: [PATCH] docs(agents): add task formatting guidelines Assisted-by: GLM 4.7 via Crush --- dot_config/AGENTS.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/dot_config/AGENTS.md b/dot_config/AGENTS.md index 2137b8e32edd31af9027fcdea17483741584039d..08e3c2ae25d1a72611fd2862be4d9bb32c9012ab 100644 --- a/dot_config/AGENTS.md +++ b/dot_config/AGENTS.md @@ -109,6 +109,10 @@ lune note add "Title" -b NOTEBOOK -c - < content.md If I specify an area but not a goal, check `lune goal list -a AREA` first. When I refer to `something/else`, I mean `area/goal`. For example, `projects/lunatask` would be `projects` area and `lunatask` goal. +#### 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 note from you to me. If including a message for future Veldt to go and implement something, leave it in a block quote underneath your note to me and be sure to greet yourself. + #### How to defer work Your suggestions are valuable and our findings while working are important. When we identify an issue, or you suggest improvements, fixes, etc., but I say we'll tackle them later, suggest creating a task with `lune` so we don't lose that information. If I directly reference something to begin our work, make sure to append a `References: {ref}` trailer for each of them so I can find them again. Try to turn the refs into web links, but project-name/commit/{hash} or project-name/pr/{number} or project-name/todo/{number} are fine to fall back on.