We only use cookies to enhance your experience. No cross-site tracking, no ads. Read our Cookie Policy.
Record your update. Your agent posts the summary, the action items, and links to the moments that matter.
Talk through what moved, what is next, and where you are stuck.
Give it the supercut link and name the channel it goes to.
A bullet per topic, the action items, and timestamped links.
Record your async video update in Supercut and let your agent write the Slack message. It reads the transcript and posts the summary to your channel, so your team gets the text, and the recording timestamped by section for anyone who wants the detail.
Connected to your agent.
Connected to your agent.
Claude, Cursor, or similar.
Talk through your update the way you would say it in the meeting. No slides, no script. Supercut transcribes as you go, so everything you say becomes something the agent can turn into a bullet. Cover the four things your team actually needs:
What you finished, and what changed because of it.
What you are picking up, and by when.
The thing that will slow you down if nobody moves it.
Say their name out loud. That is what the agent tags in Slack.
Give the supercut link to your agent and name the channel. It pulls the transcript, sentence by sentence with timestamps, and groups what you said into topics in the order you covered them.
Your agent writes a bullet per topic and lists the action items with the owners you named. If you called someone out in the video, it adds the callout to the message, so they get a notification instead of finding out later. Each bullet links to the second in the recording where you said it, so anyone who wants the full version can jump straight to the part they care about.
Record your update, then paste this to your agent. Swap [SUPERCUT LINK] for your recording and [CHANNEL] for where it should post.
Here is a supercut of my update: [SUPERCUT LINK]
Read it and post the summary to [CHANNEL] in Slack.
1. Fetch the transcript for that recording.
2. Group what I said into topics.
3. Write the Slack message with:
- A single line at the top saying what this update covers
- A bullet per topic, in my words
- Action items, with the owner named if I named them
- A link to the recording at the timestamp where each topic starts
4. Tag the people I called out by name, so it reaches them.
Rules:
- Keep it short enough to read without scrolling. If it does not fit, cut detail, not topics.
- Only list an action item if I said someone would do something. Do not invent owners or deadlines.
- Use my phrasing where it is already clear. Do not summarize the summary.The agent can only write what you said. Cover the four things above while you record and the message writes itself.
Recording the update instead of holding the meeting is the point. You go into as much detail as it deserves, and nobody has to sit through it live. The catch is that not all of that detail is relevant to everyone, so some people will not press play. The Slack message is the middle ground. Everyone reads the part that concerns them, sees the callout if it is theirs, and follows a timestamp into the video when they want the full version.
Weekly team updates, project check-ins, handovers before you go on leave. Anything you would rather say than type.
This is one of several things your agent can do across the two tools.
Record the bug happening. Your agent gets the transcript and frames, and the Linear ticket writes itself.
Explain how it should work, once. Your agent writes the stories your developers need to build it.
Point your agent to your PM's feature demo video, and it writes the help center article, screenshots included.
Record yourself doing the work once. Your agent picks it up and writes the documentation directly in your database.