How do I install the Specify skill?

Run npx skillmds@latest add nvzver/specify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Specify skill do?

Write the grounded spec — EARS requirements, user flows, and Gherkin acceptance scenarios. Output — requirements.md + .feature files. It is listed under Coding & Dev Tools on SkillMD.

Is Specify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Specify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Specify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Specify?

NVZver (@nvzver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Specify by nvzver — Agent Skill

Name: Specify
Author: NVZver

File contents

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.

Frequently asked questions

Specify