Engineering
Outer loop on Grok Bot: research first, coding agent second
One agent that researches, plans, and executes in the same context drifts.
What hurt
@doublenickk tip: one of the biggest mistakes in AI-assisted development is making one agent research, plan and execute in the same context. Use Grok Bot as the outer loop — gather from GitHub, Slack, Notion and docs, identify files and constraints, then build a structured prompt for a specialized coding agent. Tip only. Not affiliated with xAI.
What to install or create
Bot gathers + structures → coding agent executes → Bot verifies against constraints.
Bots
No new bot. Follow the first-run steps.
Plugins
GitHub
Optional
Notion
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/doublenickk/status/2117052047186866514 (credit @doublenickk).
- 2Give Grok Bot the discovery job only: repos, Slack/Notion notes, constraints.
- 3Have it output a structured prompt/handoff for your coding agent — no implementation in that chat.
- 4Run the coding agent on that handoff in its own context.
- 5Return diffs/tests to the Bot (or yourself) to check against the original constraints.
Approval fence
Coding agent changes need your review before merge; Bot must not push alone.
What to tweak
Steal discovery/execution split; mixed context distracts the executor.
Source
Shadow Nick @doublenickk · 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.