delivery

delivery is a skill for Claude Code from ribeirogab/specwright. It costs 86 tokens per session (2,542 once invoked), scanned A, original, MIT.

A workflow for delivering a large outcome by splitting it into separate software changes and assigning each ready change to an owner.

In plain words
What is it for?
Use it to decompose requirements, dispatch independent changes in parallel, track delivery state, and close out the work.
Why use it?
It tracks dependencies and progress across multiple changes, making a large project resumable and easier to coordinate.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents; mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the sw plugin — 8 skills, 8 commands, 2 agents shipped together

Good fit Use it to decompose requirements, dispatch independent changes in parallel, track delivery state, and close out the work.

Compare 6 skills from other repositories ↓
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 ribeirogab/specwright
Claude Code
/plugin install sw

Made for: Claude Code.

Or install sw, the plugin that ships this one along with the rest of its 8 skills, 8 commands, 2 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.

agentmods badge for delivery

README.md
[![agentmods](https://agentmods.dev/badge/skills/ribeirogab/specwright/delivery/github.svg)](https://agentmods.dev/skills/ribeirogab/specwright/delivery)
Your own site
<a href="https://agentmods.dev/skills/ribeirogab/specwright/delivery"><img src="https://agentmods.dev/badge/skills/ribeirogab/specwright/delivery/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.

agentmods 80×15 button for delivery

Your own site · 80×15
<a href="https://agentmods.dev/skills/ribeirogab/specwright/delivery"><img src="https://agentmods.dev/badge/skills/ribeirogab/specwright/delivery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,542 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.02542
Opus 5.5 $0.00034 $0.01017
Sonnet 5.5 $0.00017 $0.00508
Haiku 4.5 $0.00009 $0.00254

Measured 1mo ago against content hash 06710bfb54af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

delivery 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 1mo 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/sw/skills/delivery/SKILL.md · 224 lines

How it starts

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

delivery — conduct many changes to done

Take an outcome too large for one pull request and carry it to done: one change per PR, each conducted by its own owner, several at a time.

The orchestrator is a pure conductor. It reads and writes delivery state, dispatches owners, tracks, reports, and escalates. It never touches code — not one file outside the delivery folder. If you catch yourself about to implement something, stop: that work belongs to a change owner.

Announce at start: "Conducting the delivery."

Resolve bundled resources

Resolve SW_PLUGIN_ROOT as the other skills do — PLUGIN_ROOT, else CLAUDE_PLUGIN_ROOT, else two parents above this loaded skills/delivery/ directory — and require templates/delivery.md beneath it when decomposing.

Start or resume

$ARGUMENTS points at a requirements document (a PRD, a technical design, an external ticket) and no delivery exists yet → decompose it first. Read the whole document, then write .specwright/deliveries/YYYY-MM-DD-<slug>/delivery.md from the template: the outcome's why, its success criteria, and the change table with its dependency order. Write one shallow proposal.md per decomposed change, each with delivery: pointing at the delivery folder.

Keep the decomposition shallow on purpose. Each change's own plan is written later by its owner, which lets it use what the earlier changes discovered. Planning everything up front spends effort on plans that the first shipped change will invalidate.

Show the decomposition and get approval before dispatching anything.

Otherwise → locate the delivery: $ARGUMENTS names a slug, or exactly one delivery has unshipped changes (found through their delivery: frontmatter). Ask which when several match. Read delivery.md and every member change's proposal.md frontmatter.

All state lives in those files. That is what makes a fresh session able to resume with this skill and nothing else.

Commit mode

if git check-ignore -q .specwright/deliveries; then
  mode=local
  [ -d .specwright/deliveries ] || { echo "local-mode vault not found in this checkout; conduct from the checkout where specwright was initialized"; exit 1; }
else
  mode=shared
fi

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

  1. 1mo ago First seen · 224 lines · 86 tokens per session scan A 06710bfb54af

Subscribe to this mod's changes

delivery is a skill published in the GitHub repository ribeirogab/specwright (3 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 2,542 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

init-worktracking

Scaffold a portable, agent-optimized spec-driven work-tracking system into the current repository: AGENTS.md (global rules + agent reading protocol), a .tasks/ directory of atomic task files, and (by tier) ROADMAP.md, CHANGELOG.md, a validate.py checker, and thin CLAUDE.md/Cursor/Copilot pointers. Choose a footprint…

hams-ollo/zen-agent-skills · 207 tokens

new-task

Author one or more atomic, agent-ready task files for the .tasks/ work-tracking system, at a gold-standard bar. Turns a rough idea, a bug report, or a ROADMAP.md Feature into task files with honest touchedfiles, a real parent up-link, resolved dependson, and a mechanically-verifiable acceptance command, then…

hams-ollo/zen-agent-skills · 198 tokens

project-bootstrap

Bootstrap a new or bare repository with a sane, stack-matched baseline, then hand off to init-worktracking for work tracking. Detects the language and package manager, then lays down .gitignore, .editorconfig, a linter/formatter config, a LICENSE, and a README stub, without clobbering anything that already exists. Use…

hams-ollo/zen-agent-skills · 148 tokens

human-handoff

Packages the current state of a project into a handoff for a person: a business partner, a client, or a team member. Produces a document or a short message, in plain language, tuned to the reader, with internals and costs redacted when the reader is a client. Use this whenever the user wants to bring a person up to…

hams-ollo/zen-agent-skills · 209 tokens

fix-batch

Delegate a batch of independent, already-scoped task files (bugs, chores, small features) to parallel isolated agents, each sandboxed in its own git worktree, with a mandatory independent verification pass before anything is treated as mergeable. Use this whenever asked to "fix these bugs", "work through the backlog"…

hams-ollo/zen-agent-skills · 204 tokens

spec-manager

Spec-driven project iteration workflow: L1 PRD -> L2 Design -> L3 Impl -> Agent Task, with human review gates at each layer.

loki-ai-ch/spec-manager · 33 tokens