Interview Me Before Writing the Spec
You get a written spec built from your answers, rather than a long brief you had to guess at up front. It works because the agent checks the code first and asks focused multiple-choice questions, so you decide things instead of inventing them.
The prompt
Act as a senior software engineer and product analyst who turns vague ideas into clear, buildable specs.
Task: I have a half-formed idea, {rough_idea}. Interview me until you could write a spec that another developer could build from without asking questions.
Steps:
1. Read {relevant_code_area} first, so your questions reflect what already exists. Do not ask anything the code already answers.
2. Ask questions in rounds of three to five. Make each one multiple choice with a recommended option and a short reason. Wait for my answers before the next round.
3. Stop when the goal, limits, key decisions and edge cases are settled. Say so, and list any assumptions you are making.
4. Write the spec to {spec_file}.
Output: Interview rounds first. Then the spec file with these headings: Goal, Out of scope, Decisions, Edge cases, and Done when. Done when must include the exact test command {test_command} and what passing looks like.
Change the parts in curly braces. Use it for vague features where you have not worked out the details; skip it for well-specified bugs.
What happened when we ran it
We sent
Act as a senior software engineer and product analyst who turns vague ideas into clear, buildable specs. Task: I have a half-formed idea, I want to add rate limiting to our public REST API, which small business customers use to pull their invoices. We have had a few customers accidentally hammer it with scripts and slow things down for everyone. I have not decided how strict it should be or how to tell customers they have hit the limit.. Interview me until you could write a spec that another developer could build from without asking questions. Steps: 1. Read the src/api/middleware folder and the authentication code in src/auth, including how API keys are looked up and where requests are logged first, so your questions reflect what already exists. Do not ask anything the code already answers. 2. Ask questions in rounds of three to five. Make each one multiple choice with a recommended option and a short reason. Wait for my answers before the next round. 3. Stop when the goal, limits, key decisions and edge cases are settled. Say so, and list any assumptions you are making. 4. Write the spec to SPEC.md in the project root. Output: Interview rounds first. Then the spec file with these headings: Goal, Out of scope, Decisions, Edge cases, and Done when. Done when must include the exact test command npm test -- --grep "rate limit" and what passing looks like.
The model replied
Run on Claude Sonnet 5.5, 07 Nov 2026. Automatic check: 2 out of 5.
Mentioned for
Claude Code
Where it came from
Found on Web, shared by Gabriel Anhaia (DEV Community, posted 6 November): Stop Writing the Perfect Prompt. Claude Code's Docs Say Let It Interview You.
This is our own version of the idea, written and tested by us. The original may differ.