Three labeled lines beat a paragraph of vibes. Intent, context, constraints is the habit under every good Grok request.
Why this matters
A first useful message already had these parts. Most people then drift. The second ask is sloppy. The third is a mood. By the fourth, the thread is a pile of corrections and Grok is averaging them.
ICC is how you keep the brief short enough to reuse. You can type it in twenty seconds. You can say it on the phone. You can paste it at the top of a file drop. When a reply is wrong, you can point at which of the three failed: Grok missed the intent, invented context, or broke a constraint.
If you skip this, you will blame the model for being “random.” It is not random. It is under-briefed.
Teach
Write every non-trivial request as three blocks.
Intent is the outcome, not the activity. “A one-page parent note I can send tonight” is intent. “Help me with communication” is not. Intent answers: what exists when we stop?
Context is what is already true. Who, when, where, what just happened, what the reader already believes. Context is not your feelings about the week unless the feelings are the job. Two to eight lines. If a fact would change the answer, it belongs here. If it would not, leave it out.
Constraints are the rails. Length. Format. Tone. Must include. Must not. Reading level. Language. “No emojis.” “No legal advice.” “Use the numbers I gave; do not invent hours.” Constraints are how you stop Grok from being helpful in the wrong direction.
A compact shape you can reuse:
Intent: [artifact + who it is for]
Context: [what is true]
Constraints: [length, format, must, must-not]
That is enough for most desk work. Add a stop line when the job is easy to overbuild: “Stop at a draft I can edit in five minutes.”
A few patterns that keep ICC honest:
- Intent is singular. One artifact. “Email and a slide and a poem” is three intents. Split them.
- Context is sourced. Prefer facts you can point at. “The invoice is 14 days late” beats “they’ve been difficult.”
- Constraints are testable. “Keep it short” is not a constraint. “Under 120 words” is. “Professional” is not. “No slang, no apology, one ask” is.
- Defaults fill empty rails. If you do not set length, you get an essay. If you do not set must-not, you get extra advice. Empty constraints are still a choice.
ICC is not a magic spell. A bad intent, clearly written, still produces a bad artifact. “Write something impressive” will get you impressive sludge. Tighten the intent until you could hand the output to a person without explaining what you meant.
When you are in a hurry, do not drop ICC. Drop the decoration. Three blunt lines are faster than a polite paragraph and a disappointed rewrite.
Worked example
Same job, two briefs. The job is real enough to steal the shape, not the facts.
Vague:
Help me tell the crew about the schedule change.
ICC:
Intent: A 10-line notice the crew lead can read at 6:45 in the shop. They need to know what moved and what did not.
Context: Friday millings job moved from 07:00 to 09:30. County inspector lands at 08:00 and still needs the north access clear. Afternoon pour is unchanged at 13:00. Two rental saws still due back at 16:00. Crew already has the old 07:00 plan on paper.
Constraints: Plain language. No more than 10 lines. Lead with the new start time. Include who to radio if they are already en route (dispatch, not me). Do not mention the inspector’s name. Do not add a pep talk.
The vague reply will be a speech about change management. The ICC reply should be a notice. When you run both — and you will, in a minute — read them as a lead, not as a student. Which one can be taped to a door?
Notice the constraints did three different jobs. Length stopped the essay. “Lead with the new start time” set order. “Do not mention the inspector’s name” protected a person. That last one is the kind of rail people forget, then regret.
Your turn
Open grok.com. Use one new thread. You will send two messages, in order. Same job both times. Pick a job from your actual week that is not the tailboard and not the first-useful-message thread.
If you reuse a course example, you will learn nothing and the rubric will fail you.
Exercise a2-l01-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 15 min |
Copy-ready prompts
Message 1 — send this first, with only the job name filled in:
Help me with [the job in 3–8 words].
Wait for the reply. Do not correct it yet.
Message 2 — send this next, in the same thread:
Stop. Same job, new brief. Ignore the style of your last reply.
Intent: [artifact + who it is for]
Context: [what is true right now, 4–8 lines]
Constraints:
- Length:
- Format:
- Must include:
- Must not:
- Stop when I could use this after one edit.
Write only the new artifact. Then add a 4-line comparison labeled "What changed":
- Intent honored:
- Context used:
- Constraint that did the most work:
- One thing still missing unless I add it:
Artifact to paste
- Your vague message and Grok’s first reply (trim if long; keep the first screen).
- Your ICC brief and Grok’s new artifact plus the What changed block.
- One line from you: which of the three — intent, context, or constraints — was empty in the vague ask, and how you can see that in the first reply.
Rubric
- Pass: Both replies are from the same thread. The ICC brief has all three blocks with concrete content. Grok’s “What changed” block is present. Your line points at a specific miss in the first reply (invented reader, wrong length, missing fact). The job is yours.
- Fail: Only one prompt. A comparison you wrote without Grok. Two different jobs. A vague second message that just says “make it better.” You skipped opening Grok and summarized this lesson.
Common failure
The common failure is fake constraints. “Be concise, professional, and impactful.” Those words do not fail a test, so Grok cannot obey them. Replace each adjective with a number or a ban. Concise → 8 lines. Professional → no slang, no jokes, one ask. Impactful → delete it.
The other failure is stuffing intent into constraints. “Must include a warm personal brand story” is usually a confused intent. If you want a story, say so in intent. Constraints should stop things, or fix format — not hide a second job.
What’s next
You can brief. Next: stay in the thread. Most of the value is turns two through five, if you say what to keep and what to change instead of starting over.
