spec-writing

spec-writing is a skill for Claude Code, Codex from Pixel-Process-UG/superkit-agents. It costs 39 tokens per session (2,568 once invoked), scanned A, original, MIT.

A method for writing software specifications that describe required behavior and acceptance checks without dictating the implementation.

In plain words
What is it for?
It helps define features, projects, and requirements using user needs, acceptance criteria, and small release plans.
Why use it?
It keeps requirements clear and testable while leaving developers free to choose how the software is built. Given/When/Then checks make expected outcomes explicit.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit It helps define features, projects, and requirements using user needs, acceptance criteria, and small release plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pixel-process-ug/superkit-agents/spec-writing
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 Pixel-Process-UG/superkit-agents --skill spec-writing
Clone the repo
git clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agents

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/spec-writing/github.svg)](https://agentmods.dev/skills/pixel-process-ug/superkit-agents/spec-writing)
Your own site
<a href="https://agentmods.dev/skills/pixel-process-ug/superkit-agents/spec-writing"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/spec-writing/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 spec-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/pixel-process-ug/superkit-agents/spec-writing"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/spec-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,568 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.00039 $0.02568
Opus 5.5 $0.00016 $0.01027
Sonnet 5.5 $0.00008 $0.00514
Haiku 4.5 $0.00004 $0.00257

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

Security

Grade A, and why

spec-writing 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.

templates/skills/spec-writing/SKILL.md · 273 lines

How it starts

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

Specification Writing

Overview

Specifications define WHAT the software should do, never HOW. This skill applies the Jobs to Be Done (JTBD) methodology to break requirements into properly scoped, testable specification files that drive autonomous implementation. Every spec produces Given/When/Then acceptance criteria free of implementation details.

This is a RIGID skill. Every phase, gate, and format rule must be followed exactly.

The Cardinal Rule

[HARD-GATE:SPEC] Specifications must NEVER contain implementation details.

Forbidden Allowed
Code blocks or snippets Behavioral descriptions
Variable names or function signatures Observable outcomes
Technology choices ("use React", "use PostgreSQL") Capability requirements ("renders in browser", "persists data")
Algorithm suggestions ("use K-means clustering") Success criteria ("extracts 5-10 dominant colors")
Architecture patterns ("use MVC") User-facing behaviors
Library references ("use Zod for validation") Validation requirements ("rejects malformed input")

Why: Implementation-free specs preserve flexibility. The implementing agent can choose the best approach for the codebase, technology, and constraints — and change course without spec updates.

Phase 1: Jobs to Be Done (JTBD)

Identify the user's or system's jobs using this format:

When [situation], I want to [motivation], so I can [expected outcome].

Examples:

  • "When I upload an image, I want to extract its color palette, so I can use those colors in my design."
  • "When I receive an API request, I want to validate the payload, so I can reject malformed data before processing."

Gather jobs through discovery questions:

  1. Who is the user/actor?
  2. What situation triggers this need?
  3. What outcome do they want?
  4. What happens if they cannot accomplish this?

STOP after JTBD identification — present all jobs to the user for confirmation before breaking into topics.

Read the full file on GitHub · 273 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 · 273 lines · 39 tokens per session scan A 9ac57a69d23c

Subscribe to this mod's changes

spec-writing is a skill published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 2,568 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…

addyosmani/agent-skills · 75 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

chinese-documentation

A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.

jnMetaCode/superpowers-zh · 62 tokens

create-slack-app

Use when a developer wants to create, scaffold, or bootstrap a new Slack app or agent from scratch with the Slack CLI. Covers prerequisites, authentication, choosing a workspace to install into, and creating a project from a Bolt (JS or Python) template locally. Trigger on "create a Slack app", "new Bolt app", "start…

slackapi/slack-skills-plugin · 76 tokens

subagent-driven-development

A development workflow in which a fresh coding agent implements each independent task, another review checks that task, and a final review examines the complete set of changes.

jnMetaCode/superpowers-zh · 21 tokens

music

A tool for creating and working with music using Mureka, an AI music service. It handles new songs, instrumental tracks, remixes, extensions, and audio analysis.

marswaveai/skills · 109 tokens