spec-writer

spec-writer is a skill for Claude Code, Codex from tesslio/spec-driven-development-tile. It costs 85 tokens per session (740 once invoked), scanned A, original, MIT.

A writing skill for creating or updating .spec.md files that describe a feature's requirements and link those requirements to tests.

In plain words
What is it for?
Use it to turn confirmed requirements into structured specification files or update existing specifications when requirements change.
Why use it?
It gives implementation work a clear, reviewable record of expected behavior, edge cases, and how the behavior will be checked.

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/tesslio/spec-driven-development-tile/spec-writer
Any agent
npx skills add tesslio/spec-driven-development-tile --skill spec-writer
Clone the repo
git clone --depth 1 https://github.com/tesslio/spec-driven-development-tile

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-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/tesslio/spec-driven-development-tile/spec-writer.svg)](https://agentmods.dev/skills/tesslio/spec-driven-development-tile/spec-writer)
Your own site
<a href="https://agentmods.dev/skills/tesslio/spec-driven-development-tile/spec-writer"><img src="https://agentmods.dev/badge/skills/tesslio/spec-driven-development-tile/spec-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 740 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.00085 $0.00740
Opus 5 $0.00043 $0.00370
Sonnet 5 $0.00017 $0.00148
Haiku 4.5 $0.00009 $0.00074

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

Security

Grade A, and why

spec-writer 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-writer/SKILL.md · 99 lines

How it starts

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

Spec Writer

Create and maintain .spec.md files that capture functional requirements and link to their verification tests.

When to use

  • After requirement-gathering produces confirmed requirements
  • When existing specs need updating due to changed requirements
  • When implementation revealed gaps that need documenting

Steps

  1. Determine scope. Decide whether to create a new spec or update an existing one. One spec per logical unit of functionality — don't combine unrelated features.

  2. Write frontmatter. Every spec requires YAML frontmatter:

    ---
    name: Feature Name
    description: Brief description of what this spec covers
    targets:
      - ../src/path/to/implementation.py
      - ../src/path/to/related/**/*.py
    ---
    
    • name: Human-readable feature name
    • description: One-line summary
    • targets: Relative paths or glob patterns to implementation files. At least one required.
  3. Document requirements. Write clear, scannable requirements:

    • Start with an API contract code block if there's a public interface
    • Use headings to organize by feature area
    • Be specific about expected behavior and edge cases
    • Describe error handling expectations
  4. Link tests. Add [@test] links inline, next to the requirements they verify:

    - Invalid passwords return 401
      `[@test] ../tests/test_auth_invalid_password.py`
    
  5. Review against styleguide. Check the spec against the Spec Styleguide: concise, scannable, context around test links, clear headings, specific about behavior, granular test files.

  6. Save the spec. Place spec files in the project's specs/ directory with a .spec.md extension.

Complete example

---
name: Shopping Cart
description: Add, remove, and checkout operations for the shopping cart
targets:
  - ../src/cart.py
  - ../src/checkout.py
---

# Shopping Cart

## Core operations

```python
def add_item(cart_id: str, product_id: str, quantity: int) -> Cart: ...
def remove_item(cart_id: str, product_id: str) -> Cart: ...
def checkout(cart_id: str, payment_method: str) -> Order: ...

[@test] ../tests/cart/test_cart_operations.py

Quantity rules

  • Quantity must be >= 1; values <= 0 raise ValueError [@test] ../tests/cart/test_quantity_validation.py
  • Adding an existing item increments quantity instead of duplicating [@test] ../tests/cart/test_add_existing_item.py

Checkout

  • Empty cart raises CheckoutError [@test] ../tests/cart/test_empty_checkout.py
  • Out-of-stock items are removed and the user is notified [@test] ../tests/cart/test_stock_check.py

Read the full file on GitHub · 99 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. 4d ago First seen · 99 lines · 85 tokens per session scan A 9471791132f4

Subscribe to this mod's changes

spec-writer is a skill published in the GitHub repository tesslio/spec-driven-development-tile (53 stars, last pushed 5mo ago), licensed MIT. It adds 85 tokens to every session and 740 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens