Stakeholder Update Drafter
The week's tickets and incidents → Friday's update.
role pmreportingdigestdraftingbeginnerpro planorigin selfupdated 2026-10-24
01Requires
what are these? skills vs memories vs plugins →
update format: shipped / in-progress / blocked / asks memoriesaudience register: what this stakeholder group cares about vs doesn't memorieslinear pluginsgoogle-sheets mcpread access to the issue tracker and/or the week's notes permissions
02Setup — 6 steps
- 01Create the agent. Open Grok Bot → Agents → New Agent, name it
stakeholder-update. - 02Paste the prompt. Copy the prompt below into the system field.
- 03Set two memories. Format memory (your four sections) and audience memory (what this group reads vs skips).
- 04Connect the tracker. Attach Linear plugin or paste the week's closed/in-progress list.
- 05Draft Friday 15:00. Schedule a weekly draft — you still edit before it sends.
- 06Check the 'asks'. The asks section is the point — verify each ask names an owner and a date.
03Prompt
agent prompt · system field
You are a stakeholder comms agent. From this week's tickets/incidents/notes produce:
- shipped: what users can now do, in outcome language (not PR titles)
- in-progress: status + honest ETA flag where slipped
- blocked: what it needs, who from, by when
- asks: 1–3 specific requests, each with owner + date
- Filter everything through the audience memory — this group doesn't read internals.
- Under 250 words total. If a section is empty, write '—' not filler.
04Config
| name | example | description |
|---|---|---|
format memory | "shipped/in-progress/blocked/asks" | Your section structure — the prompt reads it from memory |
audience memory | "execs: outcomes only, no ticket IDs" | What to leave out matters more than what to include |
05Sample output
Example output shape: 4-section draft, 212 words, 2 asks with owners.
06Pitfalls
It reports activity, not outcomes. 'users can now X' phrasing is enforced by the prompt — if it slips, the audience memory is too weak.
Asks without owners get ignored. Reject drafts where an ask lacks owner+date — it's the only section that drives action.
07Variants
- board-update-drafter — monthly version with metrics table for the board deck
- incident-postmortem-drafter — upstream: its action items feed the 'shipped' section
- team-weekly-rollup — inward-facing sibling for the team channel
08FAQ
Which trackers does it read?
Linear via plugin; Jira/GitHub via export or MCP. A pasted 'done this week' list works too.
Can it send the update itself?
Draft only — you hit send. Stakeholder comms is the last place to hand over the pen.
Different audiences, different updates?
One memory per audience; same prompt. Execs get outcomes, partners get dates, eng gets specifics.
09Run it — or hand it to us
Tell us what you want Grok Bot to do: hello@awayhand.com
10Related templates
Competitor Change Digest
Weekly digest of competitor releases — with impact notes.
pm · marketing · 2026-10-24
Incident Postmortem Drafter
Incident channel chaos → structured postmortem draft.
ops · dev · 2026-10-24
Release Notes Drafter
Merged PRs in — readable release notes out, weekly.
dev · 2026-10-24
↩Also referenced by
unofficial template from a community-run directory — not affiliated with the product's vendor · disclaimer
New templates as they land. No hype.
Email to subscribe →