Grokbot TemplatesGrokbot Templates
All use cases

Engineering

ChatGPT review dispatcher + Grok CoS when the laptop is closed

The loop dies when you close the lid — unless review is scheduled elsewhere.

Share

What hurt

GargeyaS wrote “Building an AI engineering loop that can keep working when my laptop is closed.” He wanted planning, implementation, and independent review to keep moving with the laptop off, and without buying a new metered model API just for orchestration. ChatGPT Work/Codex already sat under his ChatGPT subscription (planning + independent Astra High review). A Grok Bot Chief of Staff ran execution and coordination. Cursor Cloud Agents implemented. GitHub held code, PRs, and checks. Notion Product Board held plans, ownership, and handoffs. The preferred event-driven GitHub→reviewer path was not fully proven for his exact Astra High + Notion writeback combo, so the pilot started with a scheduled ChatGPT Work dispatcher at 9 AM and 9 PM IST. He proved the handoff with a small README clone-command PR. The full failure matrix is not done.

What to install or create

Lived pilot, not a pasteable system prompt. Workflow arrow: Plan → Ready → Implementation → Review Ready → Independent review → Review Passed → Merge verification → Merge and delivery → Done. Freeze a versioned plan + digest. The reviewer records exact code version, target-branch version, and plan digest — a new commit invalidates the prior verdict. Reviewer publishes evidence to GitHub first, then mirrors to Notion; repairing sync is not a re-review. Reviewer stops at the verdict. CoS owns the next actions after Review Passed (recheck, merge eligibility, Standard merge, delivery, branch cleanup, Done). Auto engineering review is capped at 2 cycles (initial + one remediation); a second fail goes to the founder. Scoring, telemetry, privacy, student data, and auth are protected work: separate security/privacy review plus a founder merge. Nearby shape: tpm-john-notion-cursor. This page is the ChatGPT-scheduled independent review + Grok CoS + Cursor Cloud Agents loop — distinct.

Bots

  • Chief of Staff

    Execution and coordination. After Review Passed: recheck, merge eligibility, Standard merge, delivery, branch cleanup, Done. Stops for merge, send, spend, and protected work.

Plugins

  • Notion

    Required

Files

  • Notion Product Board for plans, ownership, and handoffs.

  • Frozen versioned plan + digest. Review record: exact code version, target-branch version, plan digest.

Routines

  • ChatGPT Work dispatcher at 9 AM and 9 PM IST. Event-driven GitHub→reviewer was not fully proven for Astra High + Notion writeback.

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 https://x.com/GargeyaS/status/2096738207891349661 (Article: Building an AI engineering loop that can keep working when my laptop is closed). Experience write-up — no pasted system prompt here.
  2. 2Put plans, ownership, and handoffs on a Notion Product Board. GitHub stays the place for code, PRs, and checks.
  3. 3Grok Bot Chief of Staff owns execution and coordination. Cursor Cloud Agents implement. ChatGPT Work/Codex does planning plus independent Astra High review under the ChatGPT subscription you already have — no new metered orchestration API.
  4. 4Start with a scheduled ChatGPT Work dispatcher at 9 AM and 9 PM IST. Do not assume event-driven GitHub→reviewer works for Astra High + Notion writeback until you have proved that combo.
  5. 5Freeze a versioned plan + digest. Reviewer records exact code version, target-branch version, and plan digest. A new commit invalidates the prior verdict. Evidence goes to GitHub first, then mirrors to Notion. Sync repair is not a re-review. Reviewer stops at the verdict.
  6. 6After Review Passed, CoS owns recheck, merge eligibility, Standard merge, delivery, branch cleanup, and Done. Cap the auto engineering review loop at 2 cycles (initial + one remediation). Second fail → you. Scoring, telemetry, privacy, student data, and auth need a separate security/privacy review and your merge.
  7. 7Prove the handoff with a small README clone-command PR first. The full failure matrix is not done — keep that honest.

Approval fence

Do not merge, send, or spend without your yes. Protected work waits for a separate security/privacy review and a founder merge.

What to tweak

Steal the split and the honesty: schedule the reviewer you already pay for; CoS moves the board after Review Passed; do not claim event-driven GitHub→Astra High + Notion writeback until you have proved it.

Source

Gargeya @GargeyaS · Original post

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

Browse templates

Related team blueprints