# 04D Sentence Review

Before I ask someone to build a feature, I need to describe the result that I want a user to achieve.
These activities form the core workflow, and every additional requirement should have a clear connection to that practical goal.
The difference between a necessary function and an interesting extra becomes important when time and attention are limited.
We must also explain the limits, including which accounts are supported and what happens when an external service is unavailable.
A request can sound simple while leaving several important decisions hidden, especially when it uses broad words such as improve or automate.
Should it suggest topics, write complete posts, schedule approved content, or publish without asking for a final review first?
A feature may be technically possible without being necessary for the current goal or appropriate for the current audience.
This statement gives us a visible action, a meaningful limit, and a practical way to review whether the implementation is correct.
You asked for a content tool; could you explain the main result you want a user to achieve in the first version?
Should the application write everything automatically, or do you want people to review the content before it becomes public?
Do we need detailed reports in the initial release, or can we leave that work until the basic workflow is useful?
I will write down these requirements and explain the limits before implementing the first feature or connecting any external accounts.