botteams.ai

Decision log team

Records what was decided and why, so the same argument is not had twice a year later.

Verified4 Bots· 2 routinesUndocumentedEvery weekday at 17:00 · Decision · SpotList decisions made today that have no written record.Weekly logEvery Friday at 15:00 · Decision · RecordDraft decision records for this week, each naming the rejected option.Watch this team

Decision log team

Records what was decided and why, so the same argument is not had twice a year later.

Bots

  • Spot Grok Bot
  • Record Grok Bot
  • Link Grok Bot
  • Recall Grok Bot
Group chat

Decision desk group chat

  • Spot Grok Bot
  • Record Grok Bot
  • Link Grok Bot
  • Recall Grok Bot
Connectors
  • Notion
  • Linear
  • Glean
  • Slack
Job
  • Spot Grok BotGrok Bot

    Notices decisions made in passing that were never written down.

    • Slack
  • Record Grok BotGrok Bot

    Drafts the decision record: what, why, what was rejected.

    • Notion
  • Link Grok BotGrok Bot

    Links decisions to the work that implements them.

    • Linear
  • Recall Grok BotGrok Bot

    Answers what was decided about a topic and when.

    • Glean
Routines2
  • Undocumented

    Owner: Spot Grok BotEvery weekday at 17:00

    List decisions made today that have no written record.

  • Weekly log

    Owner: Record Grok BotEvery Friday at 15:00

    Draft decision records for this week, each naming the rejected option.

Skills2
Notes

Sidebar section

Knowledge

Four Bots on institutional memory. Records decisions, makes none.

Run Decision log yourself

Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.

Prompt Installer for Grok Bot

Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.

# Grok Bot Teams installer

Set up a team for me called Decision log team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings, then Plugins.

From https://botteams.ai (knowledge-decisions). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Decision log · Spot Grok Bot
(Named "Decision · Spot" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Slack

Job:
Notices decisions made in passing that were never written down.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Decision log · Spot Grok Bot
- Title: Notices decisions made in passing that were never written down.
- Description: Notices decisions made in passing that were never written down. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Decision log · Record Grok Bot
(Named "Decision · Record" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Drafts the decision record: what, why, what was rejected.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Decision log · Record Grok Bot
- Title: Drafts the decision record: what, why, what was rejected.
- Description: Drafts the decision record: what, why, what was rejected. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Decision log · Link Grok Bot
(Named "Decision · Link" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear

Job:
Links decisions to the work that implements them.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Decision log · Link Grok Bot
- Title: Links decisions to the work that implements them.
- Description: Links decisions to the work that implements them. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Decision log · Recall Grok Bot
(Named "Decision · Recall" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Glean

Job:
Answers what was decided about a topic and when.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Decision log · Recall Grok Bot
- Title: Answers what was decided about a topic and when.
- Description: Answers what was decided about a topic and when. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

## 2. Create this group chat

Open a group chat with two to six of the Bots above. Do not add more than six.

### Decision desk group chat
Members (4, two to six Bots): Decision log · Spot Grok Bot, Decision log · Record Grok Bot, Decision log · Link Grok Bot, Decision log · Recall Grok Bot

## 3. Sidebar section

You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Knowledge.
Ask me to move the group chat and Bots into it.

## 4. Routines (confirm card required)

Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.

### Undocumented
Owner Bot: Decision log · Spot Grok Bot
Schedule: Every weekday at 17:00

Prompt to save (I will confirm the card):
List decisions made today that have no written record.

### Weekly log
Owner Bot: Decision log · Record Grok Bot
Schedule: Every Friday at 15:00

Prompt to save (I will confirm the card):
Draft decision records for this week, each naming the rejected option.

## 5. Connectors and how far they go

Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings, then Plugins, first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.

- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Linear: Draft. Use Linear for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Glean: Draft. Use Glean for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Slack: Ask before send. Use Slack only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Notion, Linear, Glean. That switch is account-wide and it is the only one that actually stops a write.

## 6. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.


## 7. Also

Standing instructions for every Bot on this team:

- Never delete a page. Archive it and say so.
- Draft edits, never publish over someone.

## Done when

- Named Bots exist
- Named group chat exists ("Decision desk group chat", two to six Bots)
- I have created section "Knowledge"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected

Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.

Teams that share these connectors

  • Onboarding docs

    Keeps the documents a new joiner actually reads in their first week correct, because those are the ones that mislead.

    • Notion
    • Glean
    • Google Drive
    • Slack
  • Runbooks

    Keeps operational runbooks correct, since a wrong runbook is read at the worst possible moment.

    • Notion
    • PagerDuty
    • GitHub
    • Glean
  • Findability

    Measures whether people can find what exists, and fixes the naming that stops them.

    • Glean
    • Notion
    • Google Drive