# speckit.clarify

speckit.clarify — a command that scans a feature spec for underspecified areas and asks up to 5 targeted questions to fill gaps before planning begins.

- 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.clarify.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/speckitclarify

## What it does

Building from an unclear spec means starting with guesses. speckit.clarify reads your current feature spec and audits it across nine dimensions: functional scope, data model, interaction flows, non-functional quality attributes, integrations, edge cases, constraints, terminology, and completion signals. It identifies which gaps matter for architecture, testing, or acceptance.

The command loads the spec file, runs `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` to locate your spec directory, and performs a structured coverage scan. When it finds ambiguity, it asks one question at a time—either offering a recommended answer with reasoning or presenting 2–5 discrete options. You accept the recommendation or provide your own; the clarification is recorded in memory and the next question follows. The output is an enriched spec ready for `/speckit.plan`.

If your spec is already complete or you skip clarification explicitly (e.g., for an exploratory spike), the command warns that rework risk increases downstream. Maximum 10 questions per session; each question expects a single-word or short-phrase answer, or a multiple-choice selection.

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.clarify.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.clarify.md

## When to use it
- identify incomplete specifications before development starts
- resolve ambiguous requirements with targeted structured questions
- fill gaps in data models, user flows, and non-functional requirements
- reduce rework risk at the planning phase
- prepare a spec for handoff to `/speckit.plan`

## Example prompts
- Clarify the spec before planning: /speckit.clarify
- Check specification completeness: /speckit.clarify Should we differentiate user roles?
- Skip clarification for a spike: /speckit.clarify This is exploratory, skip clarification

## Similar
- [speckit-clarify](https://affpapa.org/en/nevibecode/skills/speckit-clarify.md) — skill · 2300 installs
- [clarify-spec](https://affpapa.org/en/nevibecode/skills/clarify-spec.md) — skill · ★ 539 repo stars
- [deep-clarify](https://affpapa.org/en/nevibecode/skills/deep-clarify.md) — skill · ★ 33 repo stars
- [clarify](https://affpapa.org/en/nevibecode/skills/clarify.md) — skill · ★ 196 repo stars
- [speckit.checklist](https://affpapa.org/en/nevibecode/prompts/speckitchecklist.md) — prompt · ★ 110 repo stars
- [spec](https://affpapa.org/en/nevibecode/skills/owainlewis-spec.md) — skill · 440 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
