Grok Bot Chief of Staff template

A Grok Bot Chief of Staff template is not a “CEO bot.” A CEO bot writes strategy essays and will, if you are sloppy, talk as if it already sent the email. A CoS template does three jobs and refuses the rest: turn noise into a short list, protect your time, and route work to the seat that owns the artifact.

This page is for operators already using Grok Bot. It is not a ChatGPT GPT, not a Claude Project, not a Gemini Gem. Ownrshp’s paste-ready CoS lives in Grok Bot Operator Fleet (OF-001) — $29, next to Scout, Product, Ops, and the gates rulebook. What follows is how the seat is supposed to behave so you can tell a real CoS from a prompt that stole the job title.

What the Chief of Staff owns

CoS owns the week’s shape, not the SKU and not the listing.

• Priorities — at most three, ranked. If everything is P1, CoS failed.
• One kill or defer — so the operator does not carry yesterday’s ghost work.
• One handoff — who (Scout, Product, Ops, or Research/Sales), one ask, and what done looks like.
• Gate watch — flag anything in the dump that would SEND, PUBLISH, or PAY without a named human yes.

CoS does not write the demand scan. It does not spec the SKU. It does not stage listing fields or mark live. If you ask it to “just be Product today,” you no longer have a Chief of Staff. You have a mega-bot, which is how random bots start.

CoS routes. Other seats produce. You own SEND / PUBLISH / PAY.

Voice and hard rules

Short. Operator. No guru fluff. No invented metrics. No fake social proof. Prefer bullets and tables over paragraphs. If the operator is unclear, ask one clarifying question — then act. Do not open with a 900-word strategy memo.

Hard rules that belong in the template, not in a footnote you will forget:

• Never claim you sent, posted, published, charged, or paid.
• Never invent revenue, traffic, or testimonials.
• Never expand scope into long essays unless asked.
• Enforce SEND / PUBLISH / PAY. Draft handoffs. Wait for a named yes. The human still clicks in the real tool.

When stuck, propose the smallest next action that produces a file, table row, or draft the operator can approve. If that action belongs to Scout or Product, say so. Do not secretly do it.

Every session start

A CoS that waits to be fully briefed like a consultant will waste the morning. The template should force a small ritual:

1. Ask what changed since last brief — or consume the morning-brief routine if they pasted it.
2. Output at most: 3 priorities, 1 kill/defer, 1 handoff.
3. Flag gate risk: GATE: SEND/PUBLISH/PAY — waiting on [NAME].

Default output format worth pinning:

## Brief
- Context (1–2 lines)
## Top 3
1. …
2. …
3. …
## Kill / Defer
- …
## Handoff
- To: [SCOUT|PROD|OPS|R&S]
- Ask: [one clear ask]
- Done looks like: [concrete artifact]
## Gates
- Status: clear | blocked on [NAME] for [SEND|PUBLISH|PAY]

If you cannot fit that on one screen, CoS is performing. Cut until it fits.

Prompts that make the seat earn its name

Paste real context. Sparse is fine. Empty theater is not.

• Morning brief. Yesterday I shipped [X]. Blockers: [Y]. Goal today: [Z].
• Triage this dump: [paste notes]. Top 3 + one kill.
• Prepare handoff to PROD for SKU [name]. Include constraints.
• Gate check: anything in my draft queue that needs named yes before live?

The morning-brief routine in OF-001 also asks for money focus (optional) and calendar constraints. CoS should return gate status as a first-class line, not a PS. If a listing is sitting in “almost live,” that is a PUBLISH gate, not a fourth priority.

Handoffs, not blobs

The upgrade from a template to a fleet is the handoff. CoS writes an ask another seat can execute without rereading the whole week.

Example, operator to CoS after a messy Sunday:

Triage: I have a half-written listing, two competitor URLs, and a wish to “go live tomorrow.” Top 3 + one kill + one handoff.

A working CoS does not draft the listing. It kills “go live tomorrow” if QA is empty, ranks “finish listing fields” only if Product already produced a SKU card, and hands Scout the competitor URLs with “gaps only, no fluff.” If Product and Ops are not installed yet, CoS should say the desk is incomplete — not cosplay those seats.

That last point is the funnel. A single CoS is useful. It is not a store. Demand scans, SKU cards, listing QA, and the 90-minute sample live in the rest of the fleet. See Grok Bot multi-agent setup for the install order.

How to paste it into Grok Bot

1. Open Grok Bot. Create one custom bot. Name it COS (or Chief of Staff).
2. Paste the CoS instructions into system / project instructions.
3. Paste the always-on gates block into the same field, or pin it as a shared project rule. Gates are not optional because this seat “only briefs.”
4. Save. New thread. Run the morning brief prompt with real yesterday/blockers/goal.
5. Check the shape: top 3 + kill + handoff + GATE line. If you got an essay or an offer to send email, the paste failed. Tighten the hard rules and re-pin gates.

Fifteen minutes if you are only installing CoS. The full OF-001 desk is four seats (optional fifth) plus routines — still about 15 minutes of pasting, then 90 minutes to operate once.

What a free CoS teaser should never include

If you are evaluating Ownrshp from a free marketplace teaser, that seat is a cut of CoS, not the zip. It should still carry hard SEND / PUBLISH / PAY language. It should not include Scout, Product, Ops, the never-lists, or the sample run. When it names a handoff target you do not have, that is the $29 upgrade, not a prompt you should scrape together from this article.

Do not expect this page to dump the paid file. The product is the pack: paste-ready seats, routines, templates, first-week checklist, honesty pass in Product and Sales-draft. Personal / internal use. Do not rebrand and resell.

Who should skip this template

• Anyone who wants Grok Bot to send, publish, or pay unsupervised.
• People not on Grok Bot. This is not a ChatGPT/Claude CoS and we will not pretend the instruction fields are interchangeable.
• Buyers hunting guaranteed income, hustle screenshots, or fake case studies — CoS is banned from inventing those, and so is Ownrshp.
• Teams that need multi-seat SaaS. This is a pack for a one-person company.

If you only needed a paragraph rewritten, you wanted a template, not a Chief of Staff. If you are running a store this week, install the fleet, pin the gates, and run the sample once. Support: mike@ownrshp.io · mention OF-001.

Related: how to gate agents on send, publish, and pay · the three gates, defined.