GROK BUILD

A starter workflow for the next real task

The other nine pages in one sitting: define done, let Grok interview you, approve a plan, build a thin slice, run the tests, and read the diff before you keep it.

Figure 1: The four steps that matter most, in order: a checkable definition of done, a plan you approve, one thin slice, then tests and the diff.

1. One path you can run this week

You do not need every habit on day one. You need an order, so the next real task does not depend on memory. This is that order, in seven steps. The figure above shows the four that matter most: done, plan, slice, proof. Each step is a page of its own if you want the longer version. The links are at the bottom.

  1. Done. Write a few sentences, including the check. A test, a screen, a command, a file that must not change.
  2. Interview. Ask Grok to question you, one question at a time, and not to edit yet.
  3. Plan. /plan. Read the files it intends to touch. Edit the plan. Approve it only when the check is still in there.
  4. Handbook. Confirm AGENTS.md has the build, the test command, and the gotcha you already know. Add the gotcha if it is missing.
  5. Thin slice. One path through. Commit in the way your team commits, after you have looked at the diff of that slice.
  6. Proof. Run the named tests. Read the diff. If the change is easy to get wrong, ask a fresh session to rank the problems and not to edit.
  7. Keep or revert. If you cannot explain it, it does not stay.

2. The first hour is the brief

Spend the first hour on steps 1 to 4. People skip them because Grok is already offering to code. Let it wait. A wrong plan approved in a hurry is the long way around.

Filled in for the invoice button, the hour is ordinary. Done means a CSV with the columns Date, Vendor, and Amount, the API left alone, and the handbook’s test command green. The interview asks which page owns the button and which test file may change. The plan names those files. The slice is that button, not a new export platform.

Use a task you can finish. A button, a bug with a failing test, a script with one caller. A platform rewrite is not a starter workflow. It is how the starter workflow gets abandoned.

Layman rule: If you cannot demo the slice to a teammate, it is not a slice yet. It is a layer.

3. The build stays narrow

During the slice, new ideas go into the plan under Later. They do not go into the edit. If you need a second worker, give it a different folder or a worktree, and a written job. Two sessions in one set of files will step on each other.

Leave the default on for this first run. It asks before an edit and before a command that changes something. Approve commands you understand. Refuse the rest and ask what they are for. Always-approve is a later choice, on a repository you already trust, while you are still reading diffs.

4. The proof is the tests plus your eyes

Run the command from the handbook. Read the output, not only the sentence “they passed.” Then read the diff for files you did not name. A green suite with a surprise file is not done.

If you changed a skill or a project rule as part of the task, rerun one older task you already understood. A rule that helps today’s bug and breaks last week’s task is not a free improvement.

5. Hand it over, including what you did not do

Write down how to run it, what it must not do, and what you left in Later. That note is the handover, even when the teammate is you next Monday. A demo that only works inside the original chat is not finished. /rewind will not save you: in current versions it moves the chat back and leaves the files where they are.

For a check you will repeat, Grok can run one prompt from the shell with grok -p and then exit. That is optional. The interactive session is the right place to learn the loop.

The ten pages, in order: