Grokbot TemplatesGrokbot Templates
All use cases

Engineering

Personal software factory: Grok Bot orchestrates, Jev scores the loops

Cloud coding agents ship slop when nobody gathers context first or runs real review loops.

Share

What hurt

Ian Lapham (@ianlapham) uses Grok Bot as the orchestrator for a personal software factory: it ingests Slack, GitHub, and Notion, then kicks cloud coding agents through a graph of loops with Jev as verifier at each step. Pipeline: (1) Orchestration — PM + engineering agents gather live context and start work; (2) Planning/implementation on strong cloud models; (3) Review pass — parallel context-free sub-agents (minimize, repo prefs, bugs, anti-slop, evidence) report to Jev; critical findings go back to a coder; (4) Review pass 2 with a different model family; (5) Optional on-device testing on a remote Mac mini (pre-warmed devices, auth skills, feature-vs-plan check); (6) Fresh intent check with Jev on screenshots/video; (7) PR skill uploads evidence, watches CI bug bots, and re-loops on failure. Tip with author-published steps. Not affiliated with xAI.

What to install or create

Grok Bot context (Slack/GH/Notion) → cloud plan/code → multi-loop Jev review → optional device test → intent check → PR + CI loop.

Bots

  • PM orchestrator

    Gather Slack/GitHub/Notion context; kick planning when you are ready to start work.

  • Engineering orchestrator

    Hand context to cloud coding agents and drive the review/test/ship loops.

  • Jev verifier

    Score review findings and intent checks; send critical misses back to a coder.

Plugins

  • Notion

    Required

  • GitHub

    Required

Files

  • Planning skills (full-stack vs app-specific env setup); PR creation skill that attaches on-device evidence.

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

  1. 1Read the thread starting at https://x.com/ianlapham/status/2104690437650857993.
  2. 2Pipe Slack, GitHub, and Notion into Grok Bot with skills that keep context live; run separate PM and engineering kickoff jobs.
  3. 3Have cloud agents plan and implement with strong models, then run a context-free parallel review pass (minimize, prefs, bugs, anti-slop, evidence) scored by Jev.
  4. 4Run a second review pass on a different model family; optionally test on a pre-warmed remote Mac with auth/nav skills.
  5. 5Finish with a fresh intent check (screenshots/video + Jev), then open a PR with evidence and re-loop until CI/bug-bots pass — you approve merge.

Approval fence

Merge and production ship stay human-gated; agents may open PRs and re-loop CI only inside your rules.

What to tweak

Steal “context first, then parallel context-free review loops scored by a verifier.” Humans step in at the end, not every commit.

Source

Ian Lapham @ianlapham · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

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.

See Pro