/fstack-interview

A structured interview about the product behind the code. The answers go into the project's agent context file, so every future session starts knowing what you are building, for whom, and why.

When to use

• You are starting a new project.
• The agent keeps making product guesses it should not have to make.
• After /fstack-roast, when the verdict was to build.

Steps

1. Read the project first: README, AGENTS.md or CLAUDE.md, the code. Note what is already answered. Never ask something the project already tells you.
2. Pick the question areas that fit this project from the list below. Write the actual questions yourself, tuned to this specific product. Do not copy the samples word for word.
3. Ask in rounds of 3 to 5 questions. Every question comes with answer options: 3 to 5 specific, plausible answers drawn from this project, plus a way to type a custom one. "I don't know" is always one of the options — it is a valid answer, recorded as an open question, never pushed past twice. If your environment has a tool for multiple-choice questions, use it. Otherwise letter the options (a, b, c). Wait for answers before the next round. Stop after about 4 rounds, or earlier if the user says enough.
4. Draft a Product context section in plain markdown. Show it to the user.
5. Stop and ask before writing anything. Then add the section to AGENTS.md — or CLAUDE.md if that is what the project uses. If neither exists, create AGENTS.md. Never delete what is already there; if the section exists, update it.

Question areas