Projects Manager

Runs a team of Grok bots as a project org, with Notion as the source of truth

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

A Grok Bot projects manager. Notion is source of truth: one Projects row and a Grok Bot channel per project, tasks on a Tasks board, specialists claim work. The user decides. Agents execute. Does not do specialist work.

Description as published on the x.ai share page when last checked (2026-11-01).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
Notion
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Someone running several bots as a team who wants one coordinator keeping Notion as the single record of what's underway, without that coordinator doing the actual task work itself.

Not for

Anyone looking for a bot to do the writing, coding, or research itself, since the description is explicit that it manages the board and leaves specialist work to other bots.

What it does

The bot treats a Notion workspace as the source of truth for every project: one row per project, plus a dedicated chat channel for that project. Underneath each project sits a Tasks board where individual pieces of work live, and other specialist bots claim tasks off that board rather than being assigned by hand every time. Decisions stay with you: specialists claim and carry out the work, but what gets prioritized and approved remains the user's call, and the bot itself never does the specialist work.

First messages to try

  1. Here's a new project: [name and goal]. Create its row and channel in Notion, and show me the Tasks board before any specialist claims something.
  2. List every task currently unclaimed across all my active projects, and tell me which specialist bots would be able to claim each one.
  3. Walk me through what happens when two specialists both try to claim the same task, since the description says specialists claim work themselves.

Apps and accounts

Its description mentions Notion as the source of truth for projects and tasks, plus a Grok Bot channel per project, so it needs a connected Notion workspace and the ability to create those channels. It names no other outside app.

Cautions

  • A shared Notion workspace that several specialist bots can write to is easy to make a mess of; give this bot its own project database rather than pointing it at pages other tools already use.
  • Because it deliberately avoids doing specialist work itself, check early on that tasks are actually getting claimed and not just piling up unclaimed on the board.

Compare with: Bloks by Nadine | HealthTech Designer & DeveloperRoger by Peggens Altidor

Before you add it

Specific to this Bot, from what its description says:

  • It names Notion. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Notion ↗
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Eric Zakariasson. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev, cs68614-hash/awesome-grokbot-templates, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/projects-manager)

Or promote this template in the labelled Featured row, from $19.