write-spec

write-spec is a command for Claude Code, OpenCode from juliusz-cwiakalski/agentic-delivery-os. It costs 4 tokens per session (672 once invoked), scanned A, original, MIT.

A command that creates an authoritative written specification for a planned software change from an existing work item and planning context.

In plain words
What is it for?
Use it to create or find a change folder, record the change details in a Markdown file, and define the branch associated with the work.
Why use it?
It prevents missing or invented requirements by requiring other inputs to come from the active plan. The specification then gives later test planning and implementation planning a fixed reference.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/. Also seen: agent in frontmatter; mentions OpenCode.

Good fit Use it to create or find a change folder, record the change details in a Markdown file, and define the branch associated with the work.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/juliusz-cwiakalski/agentic-delivery-os/write-spec
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.

Clone the repo
git clone --depth 1 https://github.com/juliusz-cwiakalski/agentic-delivery-os

Made for: Claude Code, OpenCode.

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 write-spec

README.md
[![agentmods](https://agentmods.dev/badge/commands/juliusz-cwiakalski/agentic-delivery-os/write-spec/github.svg)](https://agentmods.dev/commands/juliusz-cwiakalski/agentic-delivery-os/write-spec)
Your own site
<a href="https://agentmods.dev/commands/juliusz-cwiakalski/agentic-delivery-os/write-spec"><img src="https://agentmods.dev/badge/commands/juliusz-cwiakalski/agentic-delivery-os/write-spec/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 write-spec

Your own site · 80×15
<a href="https://agentmods.dev/commands/juliusz-cwiakalski/agentic-delivery-os/write-spec"><img src="https://agentmods.dev/badge/commands/juliusz-cwiakalski/agentic-delivery-os/write-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 672 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.00004 $0.00672
Opus 5 $0.00002 $0.00336
Sonnet 5 $0.00001 $0.00134
Haiku 4.5 $0.00000 $0.00067

Measured yesterday against content hash 1abcd48002ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

write-spec 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 yesterday.

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.

.opencode/command/write-spec.md · 71 lines

What it actually says

User invocation: /write-spec <workItemRef>

Inputs other than workItemRef MUST be sourced from the active planning context; NOTHING may be invented. Resulting spec becomes authoritative input for /write-test-plan then /write-plan.

<discovery_rules> Given workItemRef:

  1. Search for existing folder: doc/changes/**/*--<workItemRef>--*/
  2. If not found, create: doc/changes/<YYYY-MM>/<YYYY-MM-DD>--<workItemRef>--<slug>/

Files:

  • Spec: chg-<workItemRef>-spec.md
  • Branch: <change.type>/<workItemRef>/<slug> </discovery_rules>
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. yesterday First seen · 71 lines · 4 tokens per session scan A 1abcd48002ff

Subscribe to this mod's changes

write-spec is a command published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (37 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 672 once invoked, about $0.0000 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-09-07.