← Back to catalog

Grok Bot is live.

Scott Metcalf records almost every meeting. A bot reads the transcript, turns commitments into Linear tasks, tracks them, and closes them. Orbit is chief of staff. Others draft email, watch for GTM hires, and log a son's Strava runs to a coach sheet.

For

You record meetings and still re-type the promises into a tracker.

When you're done

Commitments in Linear, closed when the work is done. Orbit at the front. Email drafted. New GTM hires flagged. The Strava sheet filled.

How

  1. 01
    Farm the transcript.

    Commitments become Linear tasks.

  2. 02
    Track and close.

    Done means the work is done, not just filed.

  3. 03
    Name Orbit.

    Chief of staff. You talk to this one.

  4. 04
    Draft email. Watch GTM hires.

    One job each. You send.

  5. 05
    Strava to the coach sheet.

    Personal seat. Same pattern.

Notes

What's good: task farming is one verb. Transcript in, Linear out, close when done. The catch: a line that was only exploratory still looks like a task, and Orbit plus email plus a hire watch plus Strava is a household. Get the transcript-to-Linear loop honest before you add the rest.

Prompt

Task farm
I record almost every meeting. Read the transcripts. Find anything I committed to. Turn each one into a task in Linear. Track progress. Close it when the work is done.

Skip lines that were only exploratory. If you are unsure, park the candidate and ask.

Orbit is my chief of staff. I talk to Orbit.

Email bot: draft almost every email I send. Nothing sends until I say so.

GTM watch: flag new GTM hires.

Strava bot: log my son's runs into the coach spreadsheet.

Give each bot one job. Let it operate. Bring decisions to Orbit.

Rewritten from https://www.linkedin.com/posts/scottmetcalf_grokbot-activity-7492994992882401280-EcZV

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About