---
name: deferring-work-through-lunatask
description: Captures findings, suggestions, and deferred work items in Lunatask with rich context for future sessions. Use when user says "we'll tackle this later", when you suggest improvements the user wants to defer, or when identifying issues to address separately.
compatibility: Requires Lunatask MCP tools or CLI access
license: AGPL-3.0-or-later
metadata:
  author: Amolith <amolith@secluded.site>
---

## Formatting

### Title

Titles must be:

- Useful and concise
- Conversational
- Include the project name

Example: `Implement FunctionSignature(Args) in go-lunatask`

### Status

New tasks usually get status `later`.

### Note structure

Use `[Title](lunatask://...)` syntax if deep links are needed.

```markdown
> [Warm, direct message to user—make them smile when they find this later]

---

Hello, future me! o/

[Thorough description of the work: what needs doing, why it matters, relevant context discovered during the session]

[Follow our slow and methodical planning approach: read relevant source code, documentation, and APIs before acting]

When starting this task, update status according to workflow. When finished, mark `complete`.

ID: PLACEHOLDER_ID
```

After creation, update the note to replace `PLACEHOLDER_ID` with the actual task ID from the creation response.

### References trailer

When user references external resources (issues, commits, PRs, tickets), append a `References:` section:

```markdown
References:

- https://github.com/user/repo/issues/123
- project-name/commit/abc123
- project-name/todo/456
```

Prefer web links; fall back to `project-name/type/id` format.

## Appending to existing notes

Only append—never overwrite unless explicitly asked.

Lunatask only supports full replacement, so reproduce the original note verbatim, then add:

```markdown
---

[New content here]
```

Use well-formed markdown with proper whitespace between sections.

## CLI fallback

If `lunatask` or `lune` MCP tools are unavailable, see [cli.md](references/cli.md).