1---
2name: creating-tasks-through-lunatask
3description: Creates tasks in Lunatask for todos, reminders, deferred work, and handoffs. Use when the user wants to capture something for later, whether for themselves or for a future agent session.
4compatibility: Requires Lunatask MCP or CLI tools
5license: AGPL-3.0-or-later
6metadata:
7 author: Amolith <amolith@secluded.site>
8---
9
10**Tasks**: Reminders, todos, bug reports, feature ideas. Self-contained; the note captures what and why for the user.
11
12**Handoffs**: Work a future agent will pick up in a fresh context window. Requires careful framing so the receiving agent knows where to start and what we learned. See [handoff.md](references/handoff.md) before creating these.
13
14If unclear which type, ask the user "is this a task or a handoff?"
15
16## Tone
17
18Always include a warm, friendly, personal, and conversational note from you to the user. Address them by name if you know it. Otherwise, just start with a friendly greeting omitting their name. Task notes are exclusively a friendly note from you to the user, while handoffs _also_ include a thorough prompt for another agent to pick up. See [handoff.md#tone](references/handoff.md#tone) for more detail.
19
20## Formatting
21
22### Title
23
24Titles must be clear:
25
26- Useful and concise
27- Conversational
28- Include the project name
29
30Examples:
31
32- `Accept 'complete' as status alias in lune`
33- `Implement ACP event sink in Crush`
34- `Investigate why lune habit track silently fails`
35
36### Status
37
38New tasks usually get status `later`.
39
40### Note structure
41
42**Tasks:**
43
44```markdown
45> [Friendly greeting], [context if helpful]
46>
47> [What needs doing and why]
48>
49> [Optional: relevant links, files, or commands if they'd help]
50```
51
52**Handoffs:**
53
54```markdown
55> [Friendly greeting], [context if helpful]
56>
57> [What needs doing and why]
58
59---
60
61[See references/handoff.md for how to write this section]
62```
63
64### References
65
66Include relevant links when they'd help—issues, commits, docs, files. For handoffs, gather these proactively from previous messages; for tasks, include what's useful.
67
68## Appending to existing notes
69
70Only append; never overwrite unless explicitly asked.
71
72Lunatask only supports full replacement, so reproduce the original note verbatim, then add:
73
74```markdown
75---
76
77[New content here]
78```
79
80## Surfacing tech debt
81
82While working, you may notice code smells, outdated patterns, missing tests, or other improvement opportunities related _or unrelated_ to the current task. We might also intentionally introduce tech debt, aware of the trade-offs. Don't let these observations or introductions disappear with the session; ask the user whether you should mention them.
83
84If the user confirms and it's/they're
85
86- **relevant to the handoff**: mention briefly in context section so the receiving agent is aware
87- **worth tracking separately**: suggest capturing as standalone task(s) so the user can pick up or hand off to another agent later. Even as standalone tasks, make sure to include enough context that another agent could pick it up.
88
89## Working around a Lunatask bug
90
91At the very very end of task notes or note contents, include `[editor_v2]::` on its own line.
92
93---
94
95If `lunatask` or `lune` MCP tools are unavailable, see [cli.md](references/cli.md). If the CLI is also unavailable, see [installing-lune.md](references/installing-lune.md).