# spec-elicitation

spec-elicitation conducts a rigorous interview to turn rough feature concepts into detailed technical specifications before writing code.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: Quintin Henry (https://github.com/qdhenry/)
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/spec-workflow/spec-elicitation.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/spec-elicitation

## What it does

This command forces an interview-first workflow. Claude assumes the combined persona of a principal architect and product manager, systematically probing every weak spot in your proposed idea rather than jumping straight into code generation.

The questioning covers user volume, database schema relations, third-party integrations, failure states, and compliance needs. Claude relies on the `AskUserQuestion` tool to dig into vague replies, surface conflicting requirements, and challenge edge conditions. Once all gaps are closed, it compiles the collected answers into a well-organized markdown file.

Because the configuration frontmatter explicitly targets `opus`, running this prompt without access to the larger model will degrade the depth of architectural critique.

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/spec-elicitation.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/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/spec-workflow/spec-elicitation.md

## When to use it
- Elicit exhaustive technical requirements prior to coding a non-trivial feature
- Uncover unhandled error states and boundary conditions in planned services
- Map out data retention policies and authentication rules in advance
- Generate a structured `spec.md` containing integration maps and business logic tables

## Example prompts
- /spec-elicitation
- /spec-elicitation specs/notifications.md
- Help me scope out a multi-tenant payment gateway using /spec-elicitation

## Similar
- [om-app-spec-writing](https://affpapa.org/en/nevibecode/skills/om-app-spec-writing.md) — skill · 1000 installs
- [spec-driven-development](https://affpapa.org/en/nevibecode/skills/spec-driven-development.md) — skill · 81900 installs
- [spec](https://affpapa.org/en/nevibecode/skills/owainlewis-spec.md) — skill · 440 installs
- [write-spec](https://affpapa.org/en/nevibecode/skills/write-spec.md) — skill · 3800 installs
- [cursor-spec-interviewer](https://affpapa.org/en/nevibecode/skills/cursor-spec-interviewer.md) — skill · 2700 installs
- [04-spec](https://affpapa.org/en/nevibecode/skills/04-spec.md) — skill · ★ 571 repo stars

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 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
