Stakeholder update

Stakeholder update

Invocation: user only. Drafts an update; does not send until approved.

Workflow

1. Identify the audience and cadence

From $ARGUMENTS, determine:

• Who the update is for (leadership / customer / sibling team / investor)
• Cadence (weekly / monthly / one-off)
• Delivery channel (default: email or Notion page; user can override to Slack)

Different audiences need different framing — ask if ambiguous:

• Leadership: shipped + risks + asks. Short.
• Customer: what landed for them, what's next that benefits them. Omit internals.
• Sibling team: what changed that affects them, what you need from them.

2. Pull the window

Determine the window (usually last 7 or 30 days). Gather:

• Shipped — from GitHub (merged PRs to main), Notion (pages flagged shipped), or Slack #ship
• In flight — current specs, active PRs, upcoming milestones from Notion roadmap
• Risks — from Notion risk log if role-pgm is enabled, else ask the user
• Decisions — decision log entries in Notion in the window

If the user has an existing update template in Notion (e.g. previous weeklies), fetch the most recent one and match its structure.

3. Draft

Default structure (override if template exists):

# <Audience> update — <date range>

**TL;DR** <one sentence. Biggest thing they should know.>

## Shipped
- <item> — <one-line impact>

## In flight
- <item> — <current state> — <expected landing>

## Risks / watches
- <risk> — <what we're doing>

## Asks
- <specific, actionable ask from the recipient — or "none this week">

## Context (optional)
<links to key specs, meeting recaps, decision log entries>

Voice rules:

• Three to six bullets per section. If you have more, the update isn't filtered.
• Each bullet should make sense to someone who hasn't been in standup. No inside-baseball.
• "Shipped" means customers can touch it, not "merged to main."
• Don't pad. If nothing's in flight this week, write "nothing material" and move on.

4. Review and send

Show the draft. Common edits to expect:

• "Drop the first bullet under Risks — that's resolved."
• "Add a line about ."
• "Make it shorter."

On approval, deliver via the agreed channel:

• Email: use /team-core:draft-email pattern
• Notion: create page at the team's updates path
• Slack: post to the agreed channel/DM

Don't

• Don't include confidential items in a customer update without confirming with the user.
• Don't manufacture "progress" on in-flight items. If nothing moved, say "no change."
• Don't send without explicit approval.