Lesson · 16 min
How to ask well
The difference between a wish and a spec, with patterns you can reuse.
Grok is steerable. The same model will give you a slogan, a legal-ish disclaimer, or a systems design depending on what you asked for. Vague asks get vague work. Specific asks still need judgment, but they start in the right neighborhood.
Four pieces of a prompt that holds
- 01Role or stance — who Grok is in this turn (editor, skeptical reviewer, staff engineer).
- 02Job — the artifact, not the vibe ('a 200-word update', not 'help me with this').
- 03Inputs — paste them, attach them, or say they are missing.
- 04Bar — format, length, tone, audience, and what to do when unsure (ask, infer, or refuse).
Write something about our Q3 launch.
Write a 180-word launch note for existing customers. Audience: ops managers, not engineers. Cover what changes on Sept 8, what stays the same, and one thing they should try in the first week. Use the facts in my paste. If a fact is missing, insert [NEED] rather than inventing it. No exclamation marks.
Reuse prompts that work. A good brief is an asset. Keep a short library for the jobs you do every week: rewrite for a specific reader, extract decisions from a transcript, critique a design, turn bullets into a memo.