Work
Bots live on a Trello-style board with owner, due date, and who-changed history
Work scattered in chat means you ask people what is late instead of opening one board.
What hurt
Rafael Galdino (@RafaelGaldino) runs Gestão MC: a Trello-style board where company work is cards with owner, due date, and priority — and bots create, move, and chase many of those cards. Each change lands in the card history with who did it (bots, team, or him). Morning view: overdue and waiting on him. He posted five setup steps and a copy-paste prompt. Not affiliated with xAI.
What to install or create
Four columns → every card has owner/due/priority → bots move with history → morning overdue list.
Bots
Board ops
Creates/moves cards, logs history, morning overdue brief.
Plugins
Notion
Optional
Routines
Morning overdue. Every morning. Show overdue cards and what waits on you.
The prompt
Gestão MC board setup (author-quoted)
Quoted from @RafaelGaldino — as published. Do not invent a second system prompt.
Create a task board with columns To do, In progress, Waiting, and Done. Each card has title, owner, due date, priority, and history. Give me a command line to create, move, and edit cards, recording who made each change. Every morning, show me what is overdue and what depends on me.
First run
- 1Read https://x.com/RafaelGaldino/status/2110855075551736319 (credit @RafaelGaldino).
- 2Create columns: To do, In progress, Waiting, Done.
- 3Require owner, due date, and priority on every card.
- 4Give bots commands to create/move cards and log who changed what.
- 5Schedule a morning list of overdue items and anything waiting on you.
Approval fence
Bots move cards; anything that spends or publishes still waits for you.
What to tweak
Steal the board-as-home: chat is for talk; cards are for work.
Source
Rafael Galdino @RafaelGaldino · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
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.