Lesson · 15 min
Files, context, and follow-through
How to keep a thread honest when the work spans documents and days.
Grok only knows what you put in front of it, plus what was baked in at training. A 'project' or a long thread is just a way to keep the right material in that window. The failure mode is quiet: old instructions linger, a pasted spec gets buried, and the fifth draft drifts from the first brief.
- 01Put the source of truth in the thread (or attach it). Do not assume Grok remembers a file from last week unless you can see it in context.
- 02When requirements change, say so explicitly: 'Ignore the length constraint from earlier. New bar: one page.'
- 03For multi-day work, paste a 5-line 'state of play' at the top of a new thread rather than relying on a stale one.
- 04Ask for a diff against the brief: 'List every claim in your draft that is not in my source notes.'
A practical rhythm: collect, brief, draft, interrogate, ship. Collect the inputs. Brief the job. Get a draft. Interrogate it (what's inferred, what's missing, what would a skeptic say). Then you ship — Grok does not.