Coding Agents · Power user

Plan, comment, approve: a website change with plan mode

You want a coding agent to change your website, but you want to see and approve the plan before any file changes.

  • Grok Build
  • Claude Code

For: Owner, Tech person · Updated October 25, 2026

A starting point: fill in the [brackets] with your own details, and check the answer before you use it. Tool screens change often, so yours may look a little different.

Prompt Park Sessions · Three-Minute AI for Small Business

Video walkthrough

Video coming later: Plan Before It Touches Anything: Plan Mode in Claude Code, Grok Build, Cursor, and Codex (P3-03). Until then, watch the free episodes that are out now.

The prompts

Copy the version for the tool you use, then replace every [bracket].

GROK BUILD
Type /plan (or press Shift+Tab to reach Plan). Only the plan file can be edited until you approve. Review keys: a approve, s request changes, c comment, q quit.
/plan Add [the change] to our site. Details: [details]. Put it in [where]. Follow AGENTS.md. In the plan, list every file you'll touch, what changes in each, anything you'll create, and how I can check it: [how I'll check]. Don't add libraries or change styles outside the banner.
CLAUDE CODE
Press Shift+Tab until the status bar shows plan mode, or prefix the prompt with /plan. Choose 'Yes, manually approve edits' to review each edit.
/plan Add [the change]: [details], in [where]. List the files you'll touch and why, and how I'll verify it ([how I'll check]). No new dependencies.

Fill in these [brackets]

BracketWhat to put there
[the change] e.g. a holiday-hours banner on every page
[details] e.g. Closed Nov 26–27, open 7–noon Nov 28; banner hides itself after Nov 29
[where] e.g. the shared header include, not each page
[how I'll check] e.g. open index.html and menu.html locally on desktop and phone width

Docs note (checked Oct 17, 2026): In Grok Build, plan mode lets only the session plan file be edited until you approve, and the plan review isn’t skipped even under auto or always-approve. The docs also note that plan mode gates edit tools, not the shell, so keep permissions on “ask.” In Claude Code, plan mode researches and proposes changes without editing your source; you approve with auto-accept or manual approval, or choose “No, keep planning.”

What a good answer includes (our checklist, not an AI answer):

  • Every file it plans to touch, and why
  • Nothing outside the change you asked for (no new packages, no restyling other pages)
  • A way for you to check the result in a browser, including at phone width
  • Questions about anything unclear, asked before it edits
  • No edits until you approve the plan

This one needs a real coding-agent session in your own project, so we didn’t run it in a web chat on Oct 25, 2026.

Check before you send

  • The plan touches only the files you expected
  • You commented on anything vague before approving
  • You read the diff, not just the summary
  • You checked it in a browser at phone width before publishing
  • Changes are committed in Git (or you know how to /rewind) before the next task

Privacy note: what not to paste

Don't paste hosting passwords or FTP details into the chat. Deploy yourself, after you've checked.