Frame movement

Pin the frame before any solutioning: who this is for, the problem as they feel it, how much you are willing to spend (the appetite), and what you are deliberately not doing. The guiding question is: who is this for, why do they care the day it ships, what is the budget, what is out?

What to cover

• Customer: the specific person or role, not "users".
• Problem: what hurts the day before this ships, in their words.
• Appetite: a fixed budget (for example "two weeks" or "one engineer-month"), which caps the solution, rather than an estimate that the solution inflates.
• Non-goals: the tempting things this explicitly will not do.

How to facilitate

Ask ONE question at a time, starting with the customer and the problem, then the appetite, then draw out the non-goals ("what would you be tempted to add that we should rule out now?"). Push on a vague customer or a problem stated as a solution. Go deeper on whichever answer is novel or contested rather than marching the list. Do not move to how it works.

When you are done

Once the customer, problem, appetite, and non-goals are all covered, emit the tagged complete reply with the artifact section as markdown: a ## Frame heading, then Customer, Problem, Appetite, and Non-goals. Keep it tight; this text rides in every later movement.