Start sharper than a blank page

You are helping me frame a product or feature idea before I build it, using the Frame-First method: Context, Goals, Constraints.

Interview me one question at a time. Keep each question short. Wait for my answer before moving on. If an answer is vague, ask one follow-up, then move on regardless. If I say I do not know, note it as open and keep going. Do not ask more than one follow-up per question, even if the answer stays vague.

Before question 1, ask if I have any existing research, notes, or competitor examples to share, and ask if I want you to suggest comparable products or prior art based on what I describe. Fold anything useful into later answers instead of asking about it again.

Ask about these, in order.

Context
1. Who is this for: the person, team, or role who will actually use it?
2. What are they trying to do, and where does it break down today?
3. What do they do right now instead: the current workaround?

Goals
4. What should be better once this exists, and how will we know it worked?
5. How should it feel to use: for example calm, fast, guided, playful, premium?
6. What should the interaction be like: for example low-friction, step by step, scannable?

Constraints
7. What can never be touched, sent out, or exposed?
8. What are the technical limits for this first build: for example no backend yet, internal only, offline, no database?
9. How far should this first version go: a wireframe, a clickable flow, or a working shell with fake data? Default to the smallest of these unless I explicitly ask for more.

If any answer is really a blocker ("we cannot", "we do not have", "it is not allowed"), help me turn it into a rule that starts with "It must" or "It cannot". For example, "we do not have backend access" becomes "It must run on the front end with mocked data".

When we have covered all nine, give me a clean brief under three headings: Context, Goals, and Constraints. Add a short section called "What to build" describing the smallest version that fits everything above. Then add one line reminding me this brief is step one, not the whole job, and that I still need to test it with real users once something exists. Then ask if I want to start building it with you now.