All use cases

Work

Pages for projects — stop managing work in one giant chat

One giant project chat eats usage and the bot loses the thread.

Share

What hurt

@Michael_Fenech_ (reshared in-window by @DBCrypt0): stop using chats as project management. One Page per project (goal, status, next actions, owners, deadlines, blockers, update log) + a master Projects index. Every bot reads the Page before work and updates it when done. Fresh short chats for tasks. One weekday heartbeat per project; ping you only on blocks/overdue/decisions. Start with one project for seven days. Author-quoted Chief of Staff prompt. Not affiliated with xAI.

What to install or create

One Page per project → master index → read-first/update-last → short chats → weekday heartbeat → exception-only pings.

Bots

  • No new bot. Follow the first-run steps.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • Weekday: heartbeat per project — check email/GitHub/Notion/calendar sources, verify progress, update project Page + master index; ping only on block/overdue/decision.

The prompt

Page-based project management (author-quoted)

Quoted from @Michael_Fenech_ — as published. Do not invent a second system prompt.

Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.

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.

Never send, post, spend, or buy without my explicit yes.

First run

  1. 1Read https://x.com/Michael_Fenech_/status/2115774649598705774 (credit @Michael_Fenech_; also see @DBCrypt0 reshare).
  2. 2Paste the author Chief of Staff prompt; require a proposed plan before anything is created.
  3. 3Approve one project Page + master index + one weekday heartbeat only.
  4. 4Run tasks in short fresh chats; bots must read then update the Page.
  5. 5After seven days, expand only if the Page stayed current without digging old chats.

Approval fence

Show the proposed Pages and routines first — create nothing, and never send/buy/publish/delete, without your yes.

What to tweak

Steal Pages-as-memory; chats do the work, Pages remember it.

Source

Michael | AI + Agents @Michael_Fenech_ · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro