Simple explanation
A detailed brief can prevent wrong assumptions when a task touches several files, a specific audience, or important constraints. Extra words can also introduce contradictions, outdated context, and instructions that compete with the main task.
The right amount of detail depends on the task, the tool, and the context already available. A one-file text change may need one clear sentence. A multi-step build may need a short brief, acceptance criteria, and a list of things that must not change.
The goal is not maximum length. It is sufficient, relevant, unambiguous context.
What to do
Match prompt size to task complexity:
1. State the outcome in one sentence.2. Say what already exists.3. Describe the exact change or answer you need.4. Add only constraints that affect the result.5. Request evidence or checks when the task is risky.6. Remove background that does not change the decision.
For a simple task, keep the prompt simple. For a complex task, make the important details easy to find instead of hiding them in a wall of text.
Copy-paste prompt
Goal: [one sentence]. Already exists: [one sentence]. Change or answer needed: [specific request]. Must remain unchanged: [constraints]. Before finishing, tell me what you verified and what still needs review.
Course note
Key takeaway
Match prompt length to task complexity. The best prompt has what the task needs and little that distracts from it.