1. Speed is its job. Judgment is yours.
Grok Build can read the project, edit files, and run commands. That speed is the reason to use it. It does not know which change your users will thank you for, which file is fragile, or which “small cleanup” will blow up a release.
Your leverage is four verbs: scope the job, specify what finished means, review the change, and decide what gets kept. A vague sentence produces a vague edit, quickly. A sharp sentence produces a sharp edit, also quickly. The model did not get smarter between those two. The brief did.
2. Finished has to be something you can check
Agents do better with a finish line a command or a person can test. “Make the export nicer” is a mood. “The invoice page downloads a CSV with the columns Date, Vendor, and Amount, and the existing invoice test still passes” is a finish line.
Good finish lines look like this:
- A named test passes.
- A page shows a specific control.
- A command prints a specific kind of result.
- A file you named is unchanged.
If you cannot tell a stranger how you would know the work was done, Grok cannot tell either. It will guess, and the guess will look confident.
3. Say the outcome, the limits, and show an example
Three sentences beat a page of tone. What you want. What must not change. A real file to copy.
Here is a brief you can steal and fill in. It is an example, not a Cloudadorn project:
Add a download button on the invoice page.
The file is a CSV with the columns Date, Vendor, and Amount.
Do not change the API.
Follow the button that already exists in the orders page.
Done means the current invoice test passes, and a new test covers the download.
“Follow the orders page” is stronger than “make it look modern.” One example beats a paragraph of adjectives. If the work is a bug, paste the real error. The full message, not your summary of it. The summary drops the line that mattered.
When the diff touches the API anyway, that is not a small bonus. The brief said the API stays. Send the file back by name: “Revert the API change. The button lives on the page, and the columns are Date, Vendor, and Amount.” A limit you do not enforce becomes a suggestion, and the next run will cross it again.
4. Point at the file. Do not describe the building.
In the prompt, @ attaches a file. @path/to/file:10-50 attaches a line range. Type @ and a picker opens. That is better than “somewhere in the invoice code.”
You can also ask Grok to improve the brief before it builds: “Rewrite this request so the result would be better, and ask me what is missing. Do not edit yet.” The questions it asks are often the requirements you had not written down.
5. Sometimes the point is that you learn it
If the goal is to understand a codebase, do not hand over the hard part and then skim the diff. Ask it to teach. “Walk me through how a refund is saved. Ask me a question after each step. Do not change files.” You keep the judgment you were trying to build.
One casual prompt is not a test of the tool. Try the brief above on a real task, then look at the diff yourself. The next page is when that task is big enough to plan before any code is written.