When should you use it?
- You run three or more projects with agents and lose track of who did what
- You scroll through old chats to remember why a decision was made
- Agents redo work or contradict each other because they lack the latest status
Not for: A single short task that will be finished today; Teams that already track work in a project tool their agents can read and write, unless you want a lighter layer on top; Projects with confidential material that should not sit in a page every agent can open
What do you need, and what do you get?
You need
- A lead agent that can create shared pages or documents and schedule routines
- The list of projects you want to track, with a goal for each
- Where progress shows up for each project, such as email, GitHub, Notion or your calendar
You get
- One page per project covering its goal, status, next steps, owners, due dates, decisions, blockers and a change log
- A master projects page showing status and the next step for each
- A weekday check per project that refreshes its page from the named sources
- Alerts only for blocked, overdue, changed or decision-needed items
- A closing note with outcome and lessons when a project ends
How does it work, step by step?
- Pick one projectFenech suggests piloting with a single project for a week before rolling it out.
- Paste the promptGive his prompt to your lead agent and review the proposed pages, sources and routines before approving.
- Point agents at the pageMake sure every agent working on that project can open and edit its page.
- Keep chats shortStart a new chat per task and let the page carry history and decisions.
- Judge after seven daysIf you stopped digging through old chats, extend the system to the other projects.
The prompt
The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, Claude Cowork, ChatGPT agent and others. Values in lime are placeholders.
Original prompt by Michael Fenech (@Michael_Fenech_)
Set up a Page-based project management system for my Grok Bot team. 1: PROJECT PAGES - Create one Page for each project, containing its goal, current status, next actions, task owners, deadlines, decisions, blockers and an update log showing which Bot changed what. 2: MASTER INDEX - Create a Projects Page listing every active project, its status and the next action. This becomes my single place to see what's happening across all projects. 3: READ FIRST, UPDATE LAST - Every Bot must read the relevant project Page before starting work and update that same Page when finished. Never create duplicate Pages. Don't mark work complete without checking the actual result. 4: SHORT CHATS - Use fresh chats for individual tasks instead of maintaining one enormous project conversation. The Page holds the project history, decisions and context. 5: DAILY HEARTBEAT - Create one weekday routine per project. Check relevant sources such as email, GitHub, Notion or calendars, verify progress and update the project Page and master index. 6: EXCEPTION REPORTING - Only notify me when something is blocked, overdue, needs my decision or changes status. Otherwise, keep the Pages updated without interrupting me. 7: PROJECT CLOSURE - When a project finishes, mark it Closed, record the outcome and lessons learned, and pause its heartbeat routine. Never send, purchase, publish or delete anything without my approval. Clearly flag anything unverified. Before creating anything, show me the proposed projects, their information sources and the routines you'll establish. Wait for my approval.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: a Page-based project management setup for a Grok Bot team.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Organize my projects on {platform} around shared pages instead of chat history. For each project in {project_list}: create one page with the goal, current status, next steps, who owns each step, due dates, decisions made, open blockers and a dated log of changes. Add a single overview page listing every active project with its status and next step. Every agent must open the project page before it starts and record what it did when it stops. No second pages for the same project, and nothing marked done until you have checked the real result. Each weekday, review {progress_sources} for each project, update its page and the overview, and message me only when something is blocked, late, needs my decision or changes status. When a project ends, mark it closed with the outcome and lessons, and stop its daily check. Ask me before sending, buying, publishing or deleting anything, and label anything you could not confirm. Show me the planned pages, sources and routines first and wait for my go-ahead.
What can go wrong?
- A page is only as good as its last update. Spot-check that agents really write to it when they finish.
- Without a firm rule against duplicates, agents will create a second page for the same project. Keep the master list authoritative.
- Daily checks cost usage. Pause the routine for projects that are on hold.
- Agents may mark work done from their own report. Fenech's prompt asks them to check the actual result; keep that line.
Our take
Long chat threads are a poor memory for multi-agent work: context gets buried, new chats start cold, and two agents can hold different versions of the truth. Fenech's fix is simple and borrowed from how good teams already work, a single page per project that is the record, plus a master list on top. The rule we like most is read first, update last, because it turns every agent session into a small, logged change instead of a private conversation. The exception-only reporting matters just as much, since a daily check that messages you about everything becomes noise within a week. Our caution is cost and drift: each project gets its own weekday routine, so park projects that are paused, and check now and then that the update log matches what really happened. In our dry run with a fictional three-person agency running a website rebuild and a newsletter launch, the lead agent proposed two project pages and a master list, named the inbox and a shared tracker as sources, and planned two weekday checks; it then waited for approval, and its first simulated check reported one blocked item, a missing logo file, and nothing else.
Where the time goes back: You check one page instead of rereading chats, agents start each task with the current status, and you hear only about the items that need you.
FAQ
Do I need Grok Bot Pages for this?
Will agents send anything on their own?
How many projects should I start with?
Source and credit
The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X post: a Page-based project management setup for a Grok Bot team
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Oct 29, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 30, 2026: passed. Dry-run tested by our AI test agent on sample input. Proposed before creating, kept one page per project plus a master list, exception-only report (one blocked item), approval gate respected.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 30, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.