A command for marking a task complete and choosing how to close it, such as documenting the work, creating a pull request, or merging locally.

Use it after implementation or review when you need to document the result, create or merge a pull request, or close the task in a tracker.

It provides a defined completion step so the finished work is recorded and the task is closed correctly.

done — Command for Claude Code by restarter/lets-workflow

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add restarter/lets-workflow

Claude Code

/plugin install lets

Made for: Claude Code.

Or install lets, the plugin that ships this one along with the rest of its 20 skills, 26 commands, 16 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/restarter/lets-workflow/done/github.svg)](https://agentmods.dev/commands/restarter/lets-workflow/done)

Your own site

<a href="https://agentmods.dev/commands/restarter/lets-workflow/done"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/done/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/restarter/lets-workflow/done"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 15,685 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00012	$0.15685
Opus 5.5	$0.00005	$0.06274
Sonnet 5.5	$0.00002	$0.03137
Haiku 4.5	$0.00001	$0.01569

Measured today against content hash b427a56b69e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

done scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/lets/commands/done.md · 990 lines

How it starts

The opening of the file, as written. The whole thing — 990 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Task Done

Complete the current task. Document work, create PR or merge locally, close in the tracker.

This is NOT session end. Use /lets:end to end a session. /lets:done finishes a TASK.

Convention used in this file (per CLAUDE.md "Naming Convention: LETS_*"):

{LETS_FOO} placeholder inside ```bash snippets AND AskUserQuestion strings - the orchestrator substitutes the literal value before running / before the tool call. Required because Bash tool calls are fresh shells ($LETS_FOO unset) and AskUserQuestion renders strings literally.

$LETS_FOO in prose and section headings only - read-only reference to the LETS Config inject. Do NOT use $LETS_FOO in bash blocks or AskUserQuestion strings - it silently produces wrong commands or a literal $LETS_FOO in the rendered question.

IMPORTANT: If the spec below invokes any deferred tool (e.g. AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.

Step 1: Active Task Detection

Use the detect-task skill to find the active task: Skill(skill: "lets:detect-task"). If no task found: ask user which task to close.

Epic Guard

Check the detected task's type via the tracker's show verb (beads exposes type; an adapter that doesn't expose a type can't epic-guard - skip it). If type is epic - do NOT close it automatically:

Inform user: "This is an epic. Epics stay open for future tasks."
Offer: close a specific child task instead, or confirm epic closure if user insists.

Trunk-mode Routing

Several steps below have a conditional branch for trunk-mode — when HEAD is $LETS_MERGE_BRANCH (user opted in via the take-task picker option "Stay on current branch"). The check is HEAD-based at runtime via git branch --show-current compared to $LETS_MERGE_BRANCH from LETS Config; no persistent flag.

In trunk-mode the following gates fire:

Step 4 commit range: start:..HEAD (the task boundary from .task-<slug>, not $LETS_MERGE_BRANCH..HEAD, which is empty when HEAD IS the merge-branch)
Existing-PR Guard: skip (PR on same-source-target is not a valid PR, nothing to detect)
Step 6 confirm: trunk-mode wording (push + close, no PR)
Step 7 completion comment: commit range uses start:..HEAD (same reason as Step 4)
Step 8 finish: upstream-aware push + close (tracker close verb; no PR, no merge, no git branch -d)
Step 9 output: trunk-mode "Next" options (no "Merge & close", no "Switch to merge-branch")

Read the full file on GitHub · 990 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today Changed · +4 lines b427a56b69e2
yesterday Changed 2fa01411bac6
2d ago Changed · +45 lines fe5abc2ef9db
11d ago Changed · +44 lines 0007a79de24a
19d ago Changed · +2 lines 775abd7bd8c5
20d ago Changed · +39 lines 5ac40eece3c2
24d ago Changed · +8 lines b2d1f47879c1
28d ago Changed · +2 lines d97326c8d93d
1mo ago Changed · +49 lines 3bce94e6a373
1mo ago First seen · 797 lines · 12 tokens per session scan A 759c112146d9

Subscribe to this mod's changes

done is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 15,685 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Code review Documents Git and workflow Planning ai-agents claude-code-plugin cli developer-tools

done

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Task Done

Step 1: Active Task Detection

Epic Guard

Trunk-mode Routing

What this file has done since we first saw it

Other commands, from other repositories

mr-description-creator

agy-review

release

pr

git

status