Project management on GO Pilot GO

Standup digests, blocker triage, status-report drafts, deadline watchers, and stakeholder updates for PMs running cross-functional work.

The problem

A PM's calendar is mostly meetings that exist because nobody read the doc. The real job, watching dependencies, nudging owners, drafting status, gets squeezed into the gaps. An agent fleet absorbs the watching and the drafting so the PM's actual hours go to unblocking and deciding.

Agents in the fleet

Standup digest agent. Every weekday at 8:45am, pulls yesterday's task updates from Linear or Jira, the open PRs from GitHub, and any flagged threads, then posts a one-screen digest to the team channel before standup starts.

Utterance"Every weekday at 8:45am, summarize yesterday's Linear updates and open PRs into a five-bullet standup digest and post to the engineering channel."

Blocker triage agent. Watches tickets tagged blocked. If a blocker has not had movement in 48 hours, drafts a nudge in the PM's voice to the owner with the specific ask and a suggested next step.

Status-report drafter. Friday at 3pm, drafts a weekly status email to stakeholders: what shipped, what's at risk, what's next, with a single confidence rating per workstream. PM edits one paragraph and sends.

Deadline watcher. Reads the project plan once a day. Anything inside seven days with less than 50 percent progress gets a private nudge to the owner and a flag on the PM's morning brief.

Retro prep agent. Before each retro, pulls the sprint's incidents, missed dates, and scope changes into a one-page packet so the meeting starts on data, not memory.

Workflow

  1. Plan of record lives in Linear, Jira, Asana, or a Google Sheet.
  2. Standup digest runs 8:45am, posts before the meeting.
  3. Blocker and deadline agents run hourly and at noon respectively, drafts only.
  4. Status report drafts Friday 3pm, ready for the PM's polish.
  5. Retro prep fires on a webhook from the calendar two hours before the retro.

Setup checklist

  • Connect Linear or Jira, GitHub, Slack, and Gmail via the guided OAuth in Connections.
  • Attach a markdown memory file with the team roster, RACI per workstream, escalation paths, and forbidden phrases (no false certainty).
  • Per-workstream memory: a 200-word brief per active project so the agent's status drafts reference the right owners and milestones.
  • Approval gating on any message that leaves the team channel.

Costs and capacity

CostA PM running 3 to 5 active workstreams typically lands at ~3M tokens/mo, zero voice, zero browser. Starter ($197/mo or $158/mo annual) covers it. Pro ($497/mo or $397/mo annual) makes sense for a PMO running 10 plus workstreams or stakeholder-specific digests.

Guardrails

  • Agents never reassign tickets or change due dates. Read and draft only.
  • Status drafts must cite the source ticket or PR for every claim. No confidence without evidence.
  • Stakeholder emails require human send. The agent's job is the first draft, not the relationship.

Pairs well with

Stack with the product ops fleet for release notes and feedback rollups, and the executive assistant stack for calendar and inbox load.