Have an agent prepare the pre-read for your recurring meeting
Product leader James Pember tried Grok Bot for about a week. Every other week he walks his team through new features and bug fixes in a meeting. He used to dig through release notes, GitHub and Slack to build that document. Now the bot does the prep and sends the team a finished pre-read before the meeting. He says his workflow changed more in that week than in six months, but he does not say how much time he saves.
Done with Grok BotModerate
What was done
Product leader James Pember tried Grok Bot for about a week. Every other week he walks his team through new features and bug fixes in a meeting. He used to dig through release notes, GitHub and Slack to build that document. Now the bot does the prep and sends the team a finished pre-read before the meeting. He says his workflow changed more in that week than in six months, but he does not say how much time he saves.
How to do it
- Paste the prompt into the tool, and replace the text in brackets with your own.
- Read the answer through. Do not send, delete or publish anything until you have seen it yourself.
- Check the original before you trust a figure, a name or a date.
Try it with Grok Bot
Before every [meeting name], gather what is new since the last meeting: release notes, closed issues in [repository] and important threads in [Slack channel]. Write a short pre-read with new features, bug fixes and open questions, with a link to the source for every point. Show me the draft before it goes to the team. You are done when I have approved the pre-read and it has been sent to the attendees at least one day before the meeting.
Replace text in brackets with your own.
James Pember on Substack ·