The first reply is lumber. The work is the next three turns. Starting over every time something is off is how you stay a beginner.
Why this matters
A new chat feels clean. It also throws away the brief, the file, the names, and the one paragraph that was already right. You then retype the context, miss a constraint, and get a different set of mistakes.
Grok holds the thread. That is the point of a conversation. If you treat each message as a separate wish, you are using a very expensive notepad.
This lesson is a small loop: keep, change, add. You will take a draft that is not good enough and make it usable without opening a new conversation. If you cannot do that, you do not have a method. You have luck.
Teach
When a reply is wrong, do not say “try again.” That asks Grok to roll the dice. Name the surgery.
Keep — quote or point at what already works. “Keep the three hold points and the radio line.” If you do not lock the good parts, the next draft will “improve” them into mush.
Change — name the defect and the direction. “The second paragraph lectures. Cut it to two sentences and put the time first.” Point at a line if you can. “Wrong” is not a change request.
Add — one missing fact or rail. “Add that the north gate is chained until 07:15.” Do not add a new job. A second artifact is a second pass, or a second thread.
A follow-up that works looks like this:
Keep: [the parts that stay]
Change: [the line or section + how]
Add: [one fact or constraint]
Rewrite only [the section]. Leave the rest.
“Rewrite only” matters. Without it, Grok will reprint a new document and you will play spot-the-difference.
A few rules from the field:
- Quote the failure. If a sentence is false, paste it back. Models fix text they can see faster than text you describe.
- One defect per turn when you are learning. Three complaints at once produce a compromise that still has two of them.
- Do not reload the whole ICC unless the thread lost it. A reminder is fine: “Still under 10 lines.” A full paste of the original brief every turn is how you bury the latest instruction.
- Read before you send the next fix. People stack three follow-ups while the first is still streaming. You will fight yourself.
When should you start a new thread?
- The job changed. Tailboard is done; now you want a client email. New thread.
- The context is poisoned. You experimented, role-played, or let Grok invent facts you then argued with. The model will keep smelling the experiment.
- The file set changed. New PDF, new photo, different project. Start clean and attach what this job needs.
- You cannot see the brief anymore. The thread is three screens of “no, the other one.” Summarize once — “Write a 6-line brief of what we decided” — then, if that summary is wrong, new thread with a tight ICC.
A restart is a tool. It is not a habit. The habit is to stay put and steer.
One more thing. Iteration is not nagging the model into agreeing with you. If you are asking it to confirm a decision you already made, stop. If you are asking it to hide a fact, stop. The loop is for craft, not for getting a rubber stamp.
Worked example
A shop owner asked for a voicemail script. First reply was 220 words, a joke about Mondays, and two different Saturday hours.
Turn 2 — keep / change / add:
Keep: the greeting and the weekday hours.
Change: delete the Monday joke. You wrote Saturday as 8–12 and as 9–1. The true hours are 8–12.
Add: if they need a same-day tire, say call before 10:00.
Rewrite only the script. 80 words or fewer. After the script, list any time you still are not sure about.
Turn 3 — the script is the right length, but the last line is “Have a blessed day,” which this shop does not say:
Quote: “Have a blessed day.”
Change: replace with “We’ll get you in.”
Do not touch the hours.
Turn 4 — they need a text-message twin of the same facts, not a new invention:
Keep every fact in the script. Write an SMS under 240 characters. No new offers.
Four turns, one thread, one set of facts. A restart after turn 1 would have lost the hours correction and might have invented a third Saturday.
Your turn
Open grok.com. New thread. You will deliberately get a mediocre first draft, then repair it in three follow-ups. Do not start a second chat. If you restart, the exercise is void.
Use a real artifact you would actually send or post: a notice, an email, a script, a checklist, a parent note, a short SOP. Not a poem about Grok.
Exercise a2-l02-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 18 min |
Copy-ready prompts
Message 1 — send a brief that is slightly thin on purpose (you may use ICC, but leave out one important constraint such as length or a must-not):
Intent: [artifact + reader]
Context: [what is true — include at least three facts]
Constraints: [leave out length or a must-not you care about]
Write the artifact.
After the first reply, send exactly three follow-ups, in this order. Fill the brackets.
Message 2:
Keep: [what is already right]
Change: [the main defect + the direction]
Add: [the constraint you left out]
Rewrite only the artifact. Do not add a lecture.
Message 3:
Quote this line or sentence from your last draft:
"[paste the still-wrong line]"
Change it to: [your replacement or the rule]
Do not change anything else.
Message 4:
Write a 6-line Iteration Log of this thread:
1) What the first draft got wrong
2) What turn 2 fixed
3) What turn 3 fixed
4) What still would fail if I sent this
5) Whether we stayed in one thread (yes/no)
6) Session stamp: today's date and "Iteration log written by Grok in this thread."
Then reprint the final artifact only.
Artifact to paste
- The final artifact (the reprint after message 4).
- The Iteration Log (all six lines).
- The quoted line from message 3, so it is obvious you pointed at real text.
- One sentence from you: what you would have lost if you had opened a new chat after the first reply.
Rubric
- Pass: The log’s line 5 is yes, and the thread evidence matches (quoted line appears; turn 2 and turn 3 name different fixes). Final artifact is shorter or stricter than a typical first dump. Session stamp is present. You did not start a new conversation to “clean it up.”
- Fail: One prompt and done. “Try again” with no keep/change/add. A log you authored without Grok. A new thread after the first reply. No quoted line. A final artifact that still contains the line you asked to change.
Common failure
The common failure is the polite restart. You thank Grok, open a new chat, and paste a slightly angrier version of the first brief. You feel organized. You are not. You just unpaid the thread for the same work.
The other failure is the opposite: a thread that never dies. Twenty turns, three jobs, a joke in the middle, and a file from a different site. When you cannot tell a colleague what the thread is for, start a new one. Name it. Move only the facts that still matter.
What’s next
Conversations are the skill. Module A3 is the grok.com desk: Fast vs Think, then Search, Imagine, files, and threads as tools — not as a tour of buttons.
