仕事
Pages for projects — stop managing work in one giant chat
One giant project chat eats usage and the bot loses the thread.
困っていたこと
@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.
インストールまたは作成するもの
One Page per project → master index → read-first/update-last → short chats → weekday heartbeat → exception-only pings.
ボット
新しいボットはありません。初回の手順に従ってください。
プラグイン
初日から入れるものはありません。初回の手順に従ってください。
ルーティン
Weekday: heartbeat per project — check email/GitHub/Notion/calendar sources, verify progress, update project Page + master index; ping only on block/overdue/decision.
プロンプト
Page-based project management (author-quoted)
Quoted from @Michael_Fenech_ — as published. Do not invent a second system prompt.
最終行は、こちらで加えた承認フェンスです: 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.
初回実行
- 1Read https://x.com/Michael_Fenech_/status/2115774649598705774 (credit @Michael_Fenech_; also see @DBCrypt0 reshare).
- 2Paste the author Chief of Staff prompt; require a proposed plan before anything is created.
- 3Approve one project Page + master index + one weekday heartbeat only.
- 4Run tasks in short fresh chats; bots must read then update the Page.
- 5After seven days, expand only if the Page stayed current without digging old chats.
承認フェンス
Show the proposed Pages and routines first — create nothing, and never send/buy/publish/delete, without your yes.
調整ポイント
Steal Pages-as-memory; chats do the work, Pages remember it.
出典
Michael | AI + Agents @Michael_Fenech_ · 元の投稿
xAI とは提携していません。このプロンプトは当サイトが書いたものではありません。第三者テンプレートの規約も適用されます。
Pro パック
アイデアだけでなく、完全な構成が必要ですか?
Pro パックには、人気ユースケースのジョブ本文、プロンプト、スケジュール、落とし穴が入っています。