# speckit.specify

speckit.specify builds or updates a feature specification straight from a natural language prompt. Handy for structuring requirements and acceptance criteria before writing code.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 117 repo stars
- Author: Chat2AnyLLM
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Chat2AnyLLM/awesome-claude-plugins/tree/HEAD/.claude/commands/speckit.specify.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/speckitspecify

## What it does

The command reads the feature prompt passed directly after `/speckit.specify`, extracts a short branch slug, and queries Git branches alongside local directories to figure out the next sequential number. It then launches `.specify/scripts/bash/create-new-feature.sh` to initialize the feature branch.

Next, it applies `.specify/templates/spec-template.md` to map raw notes into distinct sections: user flows, testable functional rules, and technology-agnostic success metrics. When ambiguous details surface, it allows at most three clarification placeholders to keep the scope manageable.

This setup requires the `.specify` folder with its templates and bash helper script present in the repository. Once the spec file is drafted, the command generates a dedicated validation checklist at `FEATURE_DIR/checklists/requirements.md`.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.specify.md` — Call it with /speckit.specify. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/speckit.specify.md` — Call it with /prompts:speckit.specify. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/speckit.specify.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.specify.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Chat2AnyLLM/awesome-claude-plugins/tree/HEAD/.claude/commands/speckit.specify.md

## When to use it
- turn informal feature ideas into structured specification documents
- calculate the next numeric Git branch name based on existing branches
- establish technology-agnostic success metrics and acceptance flows
- compile a quality checklist to verify requirement completeness

## Example prompts
- /speckit.specify Add user authentication with OAuth2 providers
- /speckit.specify Build an analytics dashboard for API metrics
- /speckit.specify Fix payment processing timeout on checkout

## Similar
- [speckit.companion.specify](https://affpapa.org/en/nevibecode/commands/speckitcompanionspecify.md) — command · ★ 110 repo stars
- [speckit.clarify](https://affpapa.org/en/nevibecode/prompts/speckitclarify.md) — prompt · ★ 110 repo stars
- [speckit-specify](https://affpapa.org/en/nevibecode/skills/speckit-specify.md) — skill · 2700 installs
- [specify](https://affpapa.org/en/nevibecode/skills/rudolf-s-specify.md) — skill · ★ 587 repo stars
- [spec](https://affpapa.org/en/nevibecode/skills/codewithmukesh-spec.md) — skill · 3900 installs
- [cursor-spec-interviewer](https://affpapa.org/en/nevibecode/skills/cursor-spec-interviewer.md) — skill · 2700 installs

From the same set: [chat2anyllm/awesome-claude-plugins](https://affpapa.org/en/nevibecode/by/chat2anyllm/awesome-claude-plugins.md) — 9 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
