A specification-writing skill that turns stated intent and cited code facts into requirements, user flows, and Gherkin test scenarios. Gherkin is a plain-text format for describing software behavior as tests.

Creating `requirements.md` and one `.feature` file per user flow, after a person approves the draft.

It helps turn an idea into an agreed, testable description before implementation, while keeping requirements separate from technical solutions.

specify — Skill for Claude Code by NVZver

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 NVZver/claude-marketplace --skill specify

Clone the repo

git clone --depth 1 https://github.com/NVZver/claude-marketplace

Made for: Claude Code.

Or install lsa, the plugin that ships this one along with the rest of its 7 skills, 1 agent, 1 hook.

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/skills/nvzver/claude-marketplace/specify/github.svg)](https://agentmods.dev/skills/nvzver/claude-marketplace/specify)

Your own site

<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/specify"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/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/skills/nvzver/claude-marketplace/specify"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 420 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.00033	$0.00420
Opus 5	$0.00016	$0.00210
Sonnet 5	$0.00007	$0.00084
Haiku 4.5	$0.00003	$0.00042

Measured 9d ago against content hash 50eb6917211d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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 9d 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.

lsa/skills/specify/SKILL.md · 45 lines

What it actually says

Trace. On load, print first: =============== [lsa/skills/specify/SKILL.md] [lsa] ===============

LSA Specify

See CORE.md §5 (standards) and §8 (templates).

Role

Spec author.

Goal

A grounded, technology-agnostic spec: EARS requirements, user flows, and one Gherkin scenario set per flow.

Inputs

Input	Source
Intent + cited codebase facts	`discover`

Steps

For each user flow, answer Flow / Success / I/O / Test (CORE §3). (→ user flows)
Draft EARS requirements — "While/when … the system shall …" (CORE §5). No mechanism (CORE §7). (→ draft requirements)
Draft one Gherkin .feature per flow; each Given grounded in a fact from discover (CORE §8). (→ draft scenarios)
Show the full draft spec (per core/output Rule 7 Delivery test); take human approval; then write requirements.md + the <flow>.feature files — show → approve → write per Rule 7 Authorization boundary. (→ approved spec on disk)

Output

${specs_root}/features/<name>/requirements.md + <flow>.feature files — written only after the Step 4 approval; nothing on disk before it.

Constraints

Behavior, not mechanism — libraries and APIs are the implementer's choice.
Every Given cites a real fact from discover; an ungrounded Given is [ASSUMPTION].

/lsa:specify — manual invocation.

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.

9d ago First seen · 45 lines · 33 tokens per session scan A 50eb6917211d

Subscribe to this mod's changes

specify is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 15d ago), licensed MIT. It adds 33 tokens to every session and 420 once invoked, about $0.0002 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.

Claude Code Planning Writing and docs ai-agents claude-code-marketplace claude-code-plugin prompt-engineering spec-driven-development

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…

wondelai/skills · 113 tokens

design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…

wondelai/skills · 132 tokens

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

create-app

Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…

wondelai/skills · 217 tokens

create-business

Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…

wondelai/skills · 211 tokens

cold-start-problem

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my…

wondelai/skills · 168 tokens