A task-by-task workflow for implementing a planned unit of work from a shared task ledger. It guides the agent through claiming, coding, committing, and recording proof that each task is finished.

Use it to work through feature, bug, or refactoring tasks in order, with dependencies, file ownership, commits, and completion evidence tracked.

It prevents agents from editing the same files at once or losing track of unfinished work. It also keeps implementation tied to the agreed requirements.

do — Skill for Claude Code by anton-abyzov

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 do

Clone the repo

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

Made for: Claude Code.

Or install sw, the plugin that ships this one along with the rest of its 10 skills, 1 agent, 4 hooks.

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

Your own site

<a href="https://agentmods.dev/skills/anton-abyzov/specweave/do"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/do.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 933 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.00000	$0.00933
Opus 5	$0.00000	$0.00466
Sonnet 5	$0.00000	$0.00187
Haiku 4.5	$0.00000	$0.00093

Measured 2d ago against content hash ac50e0c07552, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

do 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 2d 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.

plugins/specweave/skills/do/SKILL.md · 57 lines

How it starts

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

Do Increment

Work an increment task by task through the ledger. State lives in .specweave/increments/<id>/ledger.jsonl (append-only); tasks.md holds the definitions. Never hand-edit status lines — specweave task done renders them.

Usage

sw:do [<increment-id>]     # id optional when exactly one increment is active

Loop (repeat until `task next` returns nothing)

Pick: specweave task next <id> — prints the first open task whose deps are done and whose Files are not held by another agent. If several increments are active, pass the id.
Claim: specweave task claim T-NN <id>. Exit 3 = someone else owns it (pick another), 4 = its Files overlap a live claim, 6 = deps not done. Never edit before claiming.
Read: the task's AC: ids in spec.md and its Files:; open plan.md (or spec.md Approach) only for that scope.
Implement inside the task's Files only. Need another file → claim the task that owns it, or add a task (### T-NN Title + - AC: … | Files: … | Test: …).
Commit with the increment id in the subject: git commit -m "<id>: <what>".
Done with evidence: specweave task done T-NN <id> --run "<Test command>" (uses the task's Test: when --run is omitted). Exit 5 = the command failed → task stays open; fix and re-run. No Test: → --evidence "<sha + what you ran>". Never claim completion without a fresh, passing run.
Stuck? specweave task block T-NN <id> --reason "<what is missing>"; not needed? specweave task skip T-NN <id> --reason "<why>" (terminal).
Go to 1.

Rules

One agent per worktree when 2+ agents share the increment; branch name contains the increment id.
Append only: never edit or delete ledger lines, never touch another task's state line.
If a claim older than 2h (config tasks.leaseHours) has no done, it is stale — task next offers it again; task claim --force takes it over.
Stopping for any reason: specweave task release --all-mine then sw:handoff.
No CLI? Append the line yourself: echo '{"t":"T-01","e":"claim","by":"<agent>","at":"<ISO>"}' >> ledger.jsonl (PowerShell: [IO.File]::AppendAllText). by = SPECWEAVE_AGENT or <tool>@<host>.

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

2d ago First seen · 57 lines · 0 tokens per session scan A ac50e0c07552

Subscribe to this mod's changes

do is a skill published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 933 tokens. 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-03.

Commits Git and workflow Project management ai azure-devops claude cli developer-tools documentation

creating-issues-and-pull-requests

Use when creating GitHub pull requests or issues with template compliance. Triggers: 'create a PR', 'open a pull request', 'file an issue', 'create issue'. Also invoked by finishing-a-development-branch. NOT for: deciding whether to merge or PR (use finishing-a-development-branch).

axiomantic/spellbook · 71 tokens

version-bump

Automate version bumping in npm monorepos with CHANGELOG promotion and PR automation.

LucasSantana-Dev/sharekit · 21 tokens

work

Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.

x-cmd/x-cmd · 29 tokens

split-and-ship

Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".

tobihagemann/turbo · 61 tokens

atomic-git-discipline

Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…

damusix/atomic-claude · 106 tokens

commit-msg

You receive a git diff of staged changes via stdin. Generate a commit message.

jrswab/axe · 0 tokens