Skip to main content
command CX Codex

interview · jarrodwatts — Claude Code command: what it does, how to install

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

no license ★ 1,064 updated 2026-01-21

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/interview.md
Open on GitHub

What interview 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.

What it helps with

  • 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 for the agent

  • 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.

How to install interview

Manually: put the files in place

.claude/commands/interview.md

Call it with /interview. For all projects use ~/.claude/commands/

Questions about interview

How do I install interview in Claude Code?

Add the command file at .claude/commands/interview.md inside your project.

What does interview do?

It reads a plan file, asks detailed non-obvious questions with AskUserQuestion, then writes the revised spec back to the same file.

Which tools can the command use?

AskUserQuestion, Read, Glob, Grep, Write and Edit. There is no shell, so it will not run builds or tests.

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

interview by other authors comes first.

interview Paweł Huryn Builds customer interview scripts using The Mom Test principles or converts raw interview transcripts into structured Jobs to Be Done insights. CX Codex +1 ★ 28,211repo stars plan-interview secondsky plan-interview turns a rough plan into an implementation-ready spec through an adaptive interview. Useful when the idea exists but the requirements don't. CX Codex +1 413installs quick-spec qdhenry quick-spec reads your codebase, asks up to 10 questions and writes a focused spec file. Built for plain features and refactors where a full elicitation round is overkill. CX Codex +1 ★ 1,357repo stars deep-interview Yeachan-Heo deep-interview — a Claude Code skill that turns a vague idea into a sharp spec by asking Socratic questions. It blocks execution until ambiguity drops below a set threshold. CX Codex +1 1,100installs spec Klerith Writes technical specifications following the spec-driven method. It asks structured questions to clarify scope before saving the finalized contract into specs/. CX Codex +1 5,000installs bmad-tech-spec aj-geddes bmad-tech-spec generates a focused tech spec for small-scope work instead of a full PRD and architecture pair. Use it when requirements are clear, scope fits 1-15 stories, and you need one planning artifact before writing stories. CX Codex +1 114installs bmad-spec aj-geddes The bmad-spec Claude Code skill turns rough notes, a PRD, or a transcript into a compact SPEC.md with five sections. It activates when a project needs a clear problem statement and scope. CX Codex +1 108installs

From the same set20

The whole set →
js-min-max-loop js-min-max-loop instructs the agent to pick minimum or maximum values with a single loop instead of sorting. Avoids O(n log n) sorting costs and unnecessary array copies. CX Codex +1 ★ 1,064repo stars js-cache-property-access js-cache-property-access guides Claude Code to store deep object properties and array bounds in local variables before executing JavaScript loops. CX Codex +1 ★ 1,064repo stars js-set-map-lookups The js-set-map-lookups rule recommends using a Set when code repeatedly checks array membership. It applies to repeated lookups, such as filtering items by ID. CX Codex +1 ★ 1,064repo stars rendering-activity rendering-activity — a Claude rule that tells the agent to keep costly React components inside <Activity> so hiding them does not throw away state. CX Codex +1 ★ 1,064repo stars rendering-svg-precision rendering-svg-precision — a rule for Claude Code that reduces SVG coordinate precision to one decimal place. Applies when creating icons or editing graphics. CX Codex +1 ★ 1,064repo stars _template _template — a rule-file scaffold with fields for its title and impact, plus sections for contrasting incorrect and correct code. CX Codex +1 ★ 1,064repo stars async-parallel async-parallel — a Claude rule that sends independent async calls through Promise.all() instead of awaiting them one by one. Useful when a handler piles up sequential awaits. CX Codex +1 ★ 1,064repo stars rerender-derived-state The rerender-derived-state rule favors derived boolean state over continuously changing values, reducing React re-renders. It fits responsive UI logic. CX Codex +1 ★ 1,064repo stars

Project sponsors

Companies that keep this analytics open