Engineering
Let Grok Bot plan and check; Amp, Claude Code, and Codex do the heavy coding
Burning Grok Bot usage on raw coding eats the week before the real work is done.
What hurt
Daniel Hayes Smith (@danielhayesmith) keeps Grok Bot as the planner that also checks results. Amp, Claude Code, and Codex do the heavy coding on his own subscriptions. Every handoff spells out exactly what "done" looks like, and the planner checks the work against that before it is called done. Planner and builder do not have to be the same model. Not affiliated with xAI.
What to install or create
Plan + done criteria on Grok Bot; code on other CLIs; planner verifies.
Bots
Planner
Plans work, writes done criteria, checks builder output.
Plugins
GitHub
Optional
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/danielhayesmith/status/2111215892059116027 (credit @danielhayesmith).
- 2Tell Grok Bot it plans and verifies; coding goes to Amp / Claude Code / Codex.
- 3For each task, make the bot write an explicit "done looks like" checklist.
- 4Hand that checklist to the coding tool with the change request.
- 5Bring the result back to the planner and only mark done when the checklist passes.
Approval fence
You still approve merges and deploys. The planner only flags pass or fail.
What to tweak
Steal the split: planner checks "done"; builders spend other quotas.
Source
Daniel Hayes Smith @danielhayesmith · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.