# interview

interview runs a long question-and-answer session about a plan file and writes the finished spec back to the same path.

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

## What it does

The command opens a plan file and starts asking you questions through `AskUserQuestion`. It digs into implementation choices, interface details, risks and tradeoffs, and skips the obvious ones. When nothing is left open, it rewrites that file as a finished spec.

One markdown file holds the prompt and the tool list: `AskUserQuestion`, `Read`, `Glob`, `Grep`, `Write`, `Edit`. No shell there, so it will not run your build or test suite. It reads files and edits them. You hand it the plan path as the argument, and that path goes straight into the prompt.

The output lands in the file it read. Keep the earlier draft in git or as a copy, because the original gets overwritten.

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/interview.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/jarrodwatts/claude-code-config/tree/HEAD/commands/interview.md

## When to use it
- turn a rough plan into a spec before coding starts
- surface tradeoffs you had not considered
- fill gaps in a UI flow description
- ask the awkward questions early
- end up with one spec file instead of scattered notes

## Example prompts
- Run `/interview plans/checkout.md` and keep asking until the plan is airtight.
- \`/interview docs/auth-plan.md` — push me on the edge cases.
- Use `/interview plans/import.md` and save the result back to the file.

## Similar
- [plan-interview](https://affpapa.org/en/nevibecode/skills/secondsky-plan-interview.md) — skill · 413 installs
- [quick-spec](https://affpapa.org/en/nevibecode/commands/quick-spec.md) — command · ★ 1357 repo stars
- [deep-interview](https://affpapa.org/en/nevibecode/skills/deep-interview.md) — skill · 1100 installs
- [spec](https://affpapa.org/en/nevibecode/skills/spec.md) — skill · 5000 installs
- [bmad-tech-spec](https://affpapa.org/en/nevibecode/skills/bmad-tech-spec.md) — skill · 114 installs
- [bmad-spec](https://affpapa.org/en/nevibecode/skills/bmad-spec.md) — skill · 108 installs

## Other versions with the same name
- [interview · phuryn](https://affpapa.org/en/nevibecode/commands/interview.md) — ★ 28211 repo stars

From the same set: [jarrodwatts/claude-code-config](https://affpapa.org/en/nevibecode/by/jarrodwatts/claude-code-config.md) — 20 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
