Scope Definition

Scope constraints define the boundaries of length, depth, and breadth for the output. Without them, the model determines scope using its own heuristic for thoroughness — which tends to produce more than you need and sometimes less of what you specifically required. Scope definition is not about limiting the model; it is about specifying the deliverable. A proposal executive summary and a full analysis have different scopes. State the difference.

1. Length constraints "In 200 words or fewer." "In three bullet points." "No longer than one page." "In a single paragraph." Length constraints force specificity and prioritization. The model must decide what matters most when it cannot include everything. This decision should be guided by your priority instructions, not left to the model.
2. Depth constraints "Provide an executive-level overview, not an implementation plan." "Include technical implementation detail, not just high-level description." "Cover principles, not procedures." Depth constraints specify the level of abstraction at which the model should operate. Without them, the model guesses your preferred abstraction level.
3. Breadth constraints "Address only the financial implications." "Cover sections 2 and 4 only." "Limit to the Q3 data." "Focus exclusively on the onboarding process." Breadth constraints specify which dimensions of the topic are in scope. Without them, the model may cover aspects of the topic you do not need — often at the expense of depth on the aspects you do need.

Scope constraints have a secondary benefit: they force you to think about what the output should actually contain. If you cannot write a length constraint because you do not know how long the output should be, you probably do not know what you need yet. Scope definition is a thinking exercise as much as a prompt engineering step. When the scope constraints are hard to write, the deliverable is not yet well-defined.