A completion process for a SpecWeave work increment, meaning a tracked piece of project work. It checks that tasks are finished or skipped, runs the project's tests, linting and build checks, reviews shippable changes, updates relevant documentation and then closes the increment.

Use it to verify and close an increment, investigate failed checks, arrange a fresh-context review and prepare the branch for shipping.

Work can appear finished while tasks remain open, acceptance requirements are unmet or verification has not passed. This process makes those checks explicit before the work is marked complete.

sw-done — Skill for Claude Code by anton-abyzov/specweave

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add anton-abyzov/specweave --skill sw-done

Clone the repo

git clone --depth 1 https://github.com/anton-abyzov/specweave

Made for: Claude Code.

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/skills/anton-abyzov/specweave/sw-done/github.svg)](https://agentmods.dev/skills/anton-abyzov/specweave/sw-done)

Your own site

<a href="https://agentmods.dev/skills/anton-abyzov/specweave/sw-done"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-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/skills/anton-abyzov/specweave/sw-done"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 600 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.00045	$0.00600
Opus 5.5	$0.00018	$0.00240
Sonnet 5.5	$0.00009	$0.00120
Haiku 4.5	$0.00005	$0.00060

Measured 20d ago against content hash 905070febd36, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sw-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 20d ago.

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.

skills/sw-done/SKILL.md · 48 lines

How it starts

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

sw-done: close an increment

Closing is verify, review, complete. The one hard gate is a passing reports/verify.json; everything else is evidence.

Steps

Board. specweave task list: every task must be done or skipped. Anything open goes back to sw-do, or specweave task skip T-04 --reason "<why>".
Verify. specweave verify runs the project's test, lint and build commands (config testing.commands, else detected), checks every acceptance criterion against the ledger (an AC is met when all its tasks are done) and writes reports/verify.md and reports/verify.json. Red: fix and re-run. Do not tick AC boxes; they are derived.
Review. For anything that ships, run sw-review in a fresh context. Fix critical and high findings, then verify again.
Docs. If commands, config or user-facing behaviour changed, update README, CHANGELOG and the ## Commands table in AGENTS.md in the same branch.
Complete. specweave complete 0042. It refuses without a passing verify unless the user gives a reason: specweave complete 0042 --reason "<why>".
Ship. Push the branch and open the PR the way this repository ships; specweave report writes an HTML timeline to attach as evidence.

Report in one paragraph: verify result, review verdict (or "skipped"), commits, anything deferred.

Manual path (no CLI)

Check every task in spec.md has a done or skip line in ledger.jsonl. Run the project's test, lint and build commands yourself and put their real output in reports/verify.md. Then set "status": "completed" in metadata.json, the one state change the manual path makes by hand.

Rules

Never ask "should I close?" when the tasks are done; close, and the user can reopen.
Never edit metadata.json status while the CLI is available.
Several agents on one increment: only the lead closes, after every agent has handed off or released its claims.
Completing never calls GitHub, Jira or Azure DevOps unless close-on-complete is set; a failed sync afterwards is retried with specweave sync push.

Read the full file on GitHub · 48 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.

20d ago First seen · 48 lines · 45 tokens per session scan A 905070febd36

Subscribe to this mod's changes

sw-done is a skill published in the GitHub repository anton-abyzov/specweave (165 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 600 once invoked, about $0.0002 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-09-26.

Project management Testing ai azure-devops claude cli developer-tools documentation

product

Consolidated Galyarder Framework Product intelligence bundle.

skillmds/skillmd · 13 tokens

diet-remove

Remove a dependency identified by uzomuzo diet — analysis + issue (default) or direct PR.

future-architect/uzomuzo-oss · 22 tokens

review-story

QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.

SynkraAI/aiox-core · 42 tokens

aiox-review-story

QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.

SynkraAI/aiox-core · 44 tokens

acceptance

Test a PR review end to end and prove it honoured every guarantee in INVARIANTS.md. Use when asked to test/validate a review of a pull request, to check a finished run, or to run the 3-provider x 2-runtime acceptance matrix. Drives pr-review verify and scripts/acceptance.mjs — never hand-checks the guarantees.

guimatheus92/pr-review · 80 tokens

intent-verify

Verify current requirements against implementation and actual results across a product or change scope, including completed features. Run permissible existing checks and report findings without fixes.

ijust/intent-planner · 33 tokens