How do I install the Resuming Work Through Lunatask skill?

Run npx skillmds@latest add jeninh/resuming-work-through-lunatask in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Resuming Work Through Lunatask safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Resuming Work Through Lunatask?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Resuming Work Through Lunatask free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under AGPL-3.

Who published Resuming Work Through Lunatask?

jeninh (@jeninh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Resuming Work Through Lunatask by jeninh

Name: Resuming Work Through Lunatask
Author: jeninh

File contents

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

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.
Verify the plan still applies: check that the goal is still relevant and the suggested approach still makes sense given the current code.
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.

---name: resuming-work-through-lunataskdescription: 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.license: AGPL-3.0-or-later---## PurposeHandoff 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 acting1. 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 divergedIf 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 proceedingDon't try to reconcile the handoff with reality on your own. The user may have context about why things changed.## Surfacing tech debtWhile 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.## WorkflowWhen 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 bugAt 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](references/cli.md). If the CLI is also unavailable, see [installing-lune.md](references/installing-lune.md).

Frequently asked questions

Resuming Work Through Lunatask