resuming-work-through-lunatask

---

name: resuming-work-through-lunatask description: Resumes previously deferred work from Lunatask. Use when user pastes a task note, shares a lunatask:// deep link, says "let's pick this up", or references continuing earlier work. compatibility: Requires Lunatask MCP or CLI tools license: AGPL-3.0-or-later metadata: author: Amolith amolith@secluded.site

Purpose

Handoff notes are navigation aids, not solutions. They point you toward relevant code and context, but the codebase may have changed since the handoff was written. Your job is to explore the current state and form your own understanding.

Before acting

1. Read the actual files: entry points in the handoff tell you where to look, but always read the current source. Any code snippets in the handoff may be stale.
2. Verify the plan still applies: check that the goal is still relevant and the suggested approach still makes sense given the current code.
3. If present, follow the references: external links, commits, and docs in the handoff were included for a reason. Skim them for context.

If the code has diverged

If you find significant differences between what the handoff describes and what the code actually looks like:

• Stop
• Summarize what changed
• Wait for user input before proceeding

Don't try to reconcile the handoff with reality on your own. The user may have context about why things changed.

Surfacing tech debt

While 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.

• Mention them briefly to the user before or after completing the main work
• Offer to capture them 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.

Don't derail the primary task, but don't let useful observations vanish either.

Workflow

When you begin working on the task, update its status according to the area's workflow. When finished, mark it completed.

New tasks usually get status later, then in-progress, then lastly completed. Different workflows might have other stages, but those are core.

Working around a Lunatask bug

At the very very end of task notes or note contents, include [editor_v2]:: on its own line.

---

If lunatask or lune MCP tools are unavailable, see cli.md. If the CLI is also unavailable, see installing-lune.md.