Builder briefs before prompts
Chapter zero introduced the builder brief. This chapter sharpens it for serious prompting.
A prompt is not magic wording. It is a brief for a tool.
The five knobs are still the foundation:
- Role — who should the model act as for this task?
- Task — what exact job should it do?
- Context — what does it need to know before answering?
- Format — what shape should the output take?
- Examples — what does good look like?
For agentic coding tools and AI project workspaces, add a sixth knob:
- Constraints — what must it use, avoid, preserve, test, or not touch?
Bad prompt:
make this better
Builder brief:
Role: product editor for beginner AI education
Task: rewrite this lesson intro so it is less scary for people new to AI
Context: the learner has never used an agentic coding tool seriously
Format: 3 short paragraphs and 4 bullet points
Examples: use "tool" not "helper"; code is "moving parts"
Constraints: do not mention Python in the first paragraph; do not change file paths
The better prompt is not longer because length is good. It is longer because it removes guessing.
Most failed AI sessions are missing one of the knobs. The model guesses. You dislike the guess. Then the chat becomes a negotiation with a mistake you created upstream.
Builders do not argue with vague outputs. They improve the brief.