spec-to-done

spec-to-done is a skill for Claude Code, Codex from gozhang2/loop-engineering-kit. It costs 98 tokens per session (4,626 once invoked), scanned A, original, Apache-2.0.

A workflow for taking a software specification from review through implementation and integrated completion. It records how each acceptance requirement is supported by evidence.

In plain words
What is it for?
Use it to question unclear requirements, split work among owners, review handoffs, check merges, track evidence for each requirement, and confirm the integrated result is done.
Why use it?
It reduces the risk of declaring work finished when tasks passed separately but the whole change does not work together.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/gozhang2/loop-engineering-kit/spec-to-done
Any agent
npx skills add gozhang2/loop-engineering-kit --skill spec-to-done
Clone the repo
git clone --depth 1 https://github.com/gozhang2/loop-engineering-kit

Made for: Claude Code, Codex.

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 spec-to-done

README.md
[![agentmods](https://agentmods.dev/badge/skills/gozhang2/loop-engineering-kit/spec-to-done.svg)](https://agentmods.dev/skills/gozhang2/loop-engineering-kit/spec-to-done)
Your own site
<a href="https://agentmods.dev/skills/gozhang2/loop-engineering-kit/spec-to-done"><img src="https://agentmods.dev/badge/skills/gozhang2/loop-engineering-kit/spec-to-done.svg" alt="Measured on agentmods" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00098 $0.04626
Opus 5 $0.00049 $0.02313
Sonnet 5 $0.00020 $0.00925
Haiku 4.5 $0.00010 $0.00463

Measured 4d ago against content hash 175c4eb08e51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-to-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 4d 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/spec-to-done/SKILL.md · 385 lines

How it starts

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

Spec To Done

Drive a reviewed spec to delivered, integrated closure. The output is a closure record backed by a criterion-to-evidence ledger and a green integrated check — not a pile of individually green tasks.

This is a portable workflow, not a runtime. It works with one agent building items sequentially or a team of implementers in parallel, on any repository, task system, or none.

Treat it as a protocol, not a procedure: teams may carry the messages in JSON, markdown, issues, or PR comments. Six invariants make the loop trustworthy, whatever the carrier:

  • Every worker gets bounded work.
  • Every handback is reviewable.
  • Every gate decision explains the basis for trust or rejection.
  • Every acceptance criterion maps to evidence, a waiver, or a named blocker.
  • Every owner-only decision is escalated, never improvised.
  • Closure never overclaims.

Everything else — item sizing, ordering, tooling, how hard to inspect a given handback — is supervisor judgment, and good supervisors will invent moves this file does not list. The protocol's job is to make those moves inspectable, not to replace them.

Evidence First

"Done" in this loop is an evidence claim, not a status update. Every part of the loop exists to produce, check, or record evidence:

  • Every claim names something inspectable — a commit, diff, test, check, run, artifact, screenshot, review, trace, or recorded waiver. If a reader cannot open it, it is not evidence.
  • Evidence covers process as well as result. The result evidence says what was achieved; the work trace — how it was done — says whether to trust it.
  • The criterion-to-evidence ledger is the loop's spine. Gates read evidence against criteria; they do not read narratives, confidence, or effort.
  • No local evidence, no merge. No integrated evidence, no closure. Task-local green is not done — it is supporting evidence for one item.
  • Missing evidence is never papered over: a criterion is open, blocked, or carries a waiver recorded by the decision owner. A waiver is a decision, not missing evidence.

Read the full file on GitHub · 385 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 385 lines · 98 tokens per session scan A 175c4eb08e51

Subscribe to this mod's changes

spec-to-done is a skill published in the GitHub repository gozhang2/loop-engineering-kit (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 4,626 once invoked, about $0.0005 per session on Opus 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

codex-issue-coordinator

Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.

owainlewis/blueprint · 59 tokens

plan

Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.

owainlewis/blueprint · 42 tokens

manager

Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).

serejaris/personal-corp-os · 63 tokens

corp-doctor

Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…

serejaris/personal-corp-os · 102 tokens

pm-prioritize

Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do…

serejaris/personal-corp-os · 140 tokens

pm-roadmap

Сводит статус итерации, оценивает прогресс milestones, фиксирует изменения приоритетов, отслеживает зависимости и выдаёт roadmap в формате Now/Next/Later с атрибуцией задержек по 5 причинам, health score и фреймворком обрезки scope при нехватке ресурсов. User-invoked only — do NOT auto-trigger. Triggers on…

serejaris/personal-corp-os · 128 tokens