docs(agents): migrate lunatask to skills

Amolith created

Change summary

dot_config/AGENTS.md        | 10 ----------
dot_config/crush/crush.json | 11 -----------
2 files changed, 21 deletions(-)

Detailed changes

dot_config/AGENTS.md 🔗

@@ -27,13 +27,3 @@ When I provide the URL to or number of a ticket, todo, or issue, use the appropr
 ## Planning before acting
 
 IMPORTANT: When I ask you to plan first, I want you to first slow down and make sure you're taking your time and deliberating prior to jumping in and fulfilling my request. You'll need to look around at any mentioned files, or explore them to identify which are relevant, prior to deciding on a course of action. Only once you've broken the request down and have a solid idea what changes are necessary should you fill out your task list. Once you've made the plan, stop and ask me to review it. Once I explicitly confirm, you may get started.
-
-## Lunatask
-
-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.
-
-## 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 in Lunatask 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.

dot_config/crush/crush.json 🔗

@@ -15,17 +15,6 @@
 		"context7": {
 			"type": "http",
 			"url": "https://mcp.context7.com/mcp"
-		},
-		"lunatask": {
-			"type": "stdio",
-			"command": "lune",
-			"args": [
-				"mcp",
-				"-t",
-				"stdio",
-				"--enabled-tools",
-				"get_timestamp,create,update,delete,query"
-			]
 		}
 	},
 	"options": {