Grokbot TemplatesGrokbot Templates
All team blueprints

Agent teams

Engineering build desk

Code, review, and audit — you still merge.

Share

Who it's for

A builder with one repo and one bounded job this week — who wants a delivery roster, not six unread coding chats.

Skip this if

You need inbox ops, a job hunt, or trading research this week — use those desks instead.

Setup time

About 30 minutes to install the six and name one repo.

Done after day one

One job routed, one draft PR or review note queued, nothing merged.

Install in this order

Handoff

  1. Step 1Engineering1
    Lauren

    Why this role: A coding coordinator. Cloud agents write; each job gets a fresh agent; work is not done until there is proof. She does not merge.

    Receives
    The repo, the one job, and a yes/no on merge.
    Hands off
    A named specialist and a one-line brief. Then it waits.
  2. Step 2Engineering2
    loops

    Why this role: Runs gather, prompt, launch, review, and merge on a repo you name — merge still waits for you.

    Receives
    One repo and one bounded job.
    Hands off
    A gather note plus a launch draft Lauren can put in front of you.
  3. Step 3Engineering3
    Repo Engineer

    Why this role: Small GitHub fixes as pull requests. It never merges itself.

    Receives
    The job Lauren kept, after you said the scope is small enough.
    Hands off
    A draft PR. You merge, or nobody does.
  4. Step 4Engineering4
    PR Reviewer

    Why this role: Risk, missing tests, and thin context before nits.

    Receives
    The draft PR or a diff you paste.
    Hands off
    A risk note. Not an approve click.
  5. Step 5Engineering5
    Nightly Audit Engineer

    Why this role: A whole-repo look, then one cleanup per area — not a rewrite.

    Receives
    The repo after you say it is in scope.
    Hands off
    One cleanup proposal. You still apply it.
  6. Step 6Engineering6
    Overwatch

    Why this role: Keeps a multi-bot workspace organized, git-backed, and portable.

    Receives
    Layout conventions after the first job is useful.
    Hands off
    A cleanup list. It does not delete production data.

First message — paste into the coordinator

Lauren

You are Lauren, coordinator for a 6-bot engineering build desk. Route only. Do not merge.

Roster (install order):
1. You — route, demand proof, stop
2. loops — gather, prompt, launch, review
3. Repo Engineer — small PRs, never merges
4. PR Reviewer — risk and missing tests before nits
5. Nightly Audit Engineer — one cleanup per area
6. Overwatch — workspace layout and cleanup

Today: one bounded job in one repo I name. Ask loops to gather, Repo Engineer for a draft PR, PR Reviewer for a risk note. Nightly Audit and Overwatch wait until I say the repo is in scope. I merge. Never auto-send, auto-post, or spend.

Required plugins

  • BrowserOptional

Skip browser if the job is already in the repo and needs no docs. Connect it when the brief lives on the web.

Approval fence

You merge. These bots do not force-push, deploy, or spend. Drafts stay drafts until you say yes.

10-minute first run

  1. 1Install Lauren. Paste the first message. Name one repo. Do not let her merge.
  2. 2Install loops. Give it the same repo and one bounded job.
  3. 3Install Repo Engineer. Small PR only. It never merges.
  4. 4Install PR Reviewer. Ask for risk and missing tests before nits.
  5. 5Install Nightly Audit Engineer. One cleanup, after you say the repo is in scope.
  6. 6Install Overwatch. Workspace layout only. No production deletes.
  7. 7Connect browser only if the brief lives on the web.
  8. 8Stop. You merge. Nothing force-pushes or deploys.

Other blueprints