What is speckit.specify?

A command that turns a user's feature idea into a written specification saved as spec.md. A specification describes expected behavior, user scenarios, and testable success conditions.

Use it to define a feature's requirements and create the feature directory record used by later planning commands.

It gives development work a shared, checkable description before implementation begins.

speckit.specify — Command for Claude Code by github/spec-kit

About the project

Spec Kit is an open-source toolkit for defining software requirements and plans before implementation with an AI coding agent. It is used by developers and organizations following a spec-driven development process.

github/spec-kit · 147,879 stars · on GitHub

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/github/spec-kit

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/github/spec-kit/speckit.specify/github.svg)](https://agentmods.dev/commands/github/spec-kit/speckit.specify)

Your own site

<a href="https://agentmods.dev/commands/github/spec-kit/speckit.specify"><img src="https://agentmods.dev/badge/commands/github/spec-kit/speckit.specify/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/github/spec-kit/speckit.specify"><img src="https://agentmods.dev/badge/commands/github/spec-kit/speckit.specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 143 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.00143
Opus 5.5	$0.00004	$0.00057
Sonnet 5.5	$0.00002	$0.00029
Haiku 4.5	$0.00001	$0.00014

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

Security

Grade A, and why

speckit.specify 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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

speckit.specify — 100% identical, 0 lines differ

presets/lean/commands/speckit.specify.md · 24 lines

What it actually says

User Input

$ARGUMENTS

Outline

Ask the user for the feature directory path (e.g., specs/my-feature). Do not proceed until provided.
Create the directory and write .specify/feature.json:
```
{ "feature_directory": "<feature_directory>" }
```
Create a specification from the user input and store it in <feature_directory>/spec.md.
- Overview, functional requirements, user scenarios, success criteria
- Every requirement must be testable
- Make informed defaults for unspecified details

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.

2mo ago First seen · 24 lines · 10 tokens per session scan A 9d68997ce418

Subscribe to this mod's changes

speckit.specify is a command published in the GitHub repository github/spec-kit (147,879 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 143 once invoked, about $0.0000 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-30.

Planning ai copilot development engineering prd spec

speckit.specify next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speckit.specifygithub/spec-kit	Command	148k	yesterday	MIT	A	10	Claude Code
book-internalizewordflowlab/novel-writer	Command	957	1y ago	MIT	A	0	Claude Code
book-stylewordflowlab/novel-writer	Command	957	1y ago	MIT	A	0	Claude Code
stardust-sessionwordflowlab/novel-writer	Command	957	1y ago	MIT	A	0	Claude Code
book-characterswordflowlab/novel-writer	Command	957	1y ago	MIT	A	0	Claude Code
book-formulawordflowlab/novel-writer	Command	957	1y ago	MIT	A	0	Claude Code
book-rhythmwordflowlab/novel-writer	Command	957	1y ago	MIT	A	0	Claude Code