# 04B Keeping the Scope Clear

A request can sound simple while leaving several important decisions hidden, especially when it uses broad words such as improve or automate.
If I say that a tool should automate content, someone still needs to know which actions the tool should actually perform.
Should it suggest topics, write complete posts, schedule approved content, or publish without asking for a final review first?
I separate these choices and describe what belongs in the first release, what can wait, and what requires a human decision.
I also distinguish between things the system can do and things it is allowed to do on someone's behalf.
A feature may be technically possible without being necessary for the current goal or appropriate for the current audience.
When the scope is written clearly, it becomes easier to ask focused questions instead of repeatedly changing the entire plan.
A useful requirement might say that the application can save a draft but must not publish it until the user confirms.
This statement gives us a visible action, a meaningful limit, and a practical way to review whether the implementation is correct.
The first release does not need every possible function; it needs enough carefully chosen functions to support one complete and useful workflow.