<aside> 🚀

Turn raw release chatter into stakeholder-ready updates without manual rewrite work

This agent reviews approved product update sources, summarizes what shipped, and publishes a clean release report for downstream teams.

For product, engineering, and customer-facing teams, it creates a repeatable communication loop so important context does not get lost between ship and share.

At Notion, Product Release Report publishes daily stakeholder-ready summaries, saving ~2 hours per release cycle that would otherwise go to manual rewriting and stakeholder updates.

</aside>

How it works

• Checks approved release sources daily — release channels, release notes docs, and product update pages — for newly shipped items.
• Separates signal from noise by identifying what actually shipped, what changed, and which details matter for downstream teams.
• Publishes stakeholder-ready reports with the update name, plain-language summary, customer impact, and follow-up context.
• Flags unclear updates for review instead of guessing, speculating on unreleased work, or filling gaps with unsupported claims.

Build your own

1. What to have ready before you start

• Your workflow: The sequence of steps the agent runs, from trigger to final report. Know this before you build.

  For Product Release Report:

  1. Agent checks approved release sources on a daily schedule.
  2. Agent identifies newly posted or newly changed release items.
  3. Agent summarizes each relevant update in a consistent report format.
  4. Agent publishes the report to the destination page or channel.

• Context it needs: The information the agent draws on to understand what shipped and where to publish the finished report. You'll swap these into the starter prompt in step 2.

  For Product Release Report:

  • [ ] Main release channel → [RELEASE CHANNEL]
  • [ ] Release notes doc → [RELEASE NOTES DOC]
  • [ ] Canonical product update page → [CANONICAL PRODUCT UPDATE PAGE]
  • [ ] Destination page or channel → [DESTINATION PAGE OR CHANNEL]
  • [ ] Review owner or escalation path → [REVIEW OWNER OR ESCALATION PATH]

• Tools to connect: The apps the agent needs access to for reading updates and publishing the report.

  For Product Release Report:

  • [ ] :slack-logo-transparent: Slack (to review release channels and post report notifications)
  • [ ] :notion: Notion (to read release docs, review product update pages, and publish reports)

2. Copy and paste this starter prompt

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" />

In your left-hand sidebar, go to the Agents section and click the + button.

</aside>

You are a release reporting agent for the [TEAM NAME] team. Each day, review [RELEASE CHANNEL], [RELEASE NOTES DOC], and [CANONICAL PRODUCT UPDATE PAGE] for new approved product updates. Summarize each relevant item in plain language, explain why it matters, and publish a dated report to [DESTINATION PAGE OR CHANNEL]. Include the update name, what shipped, customer or team impact, and any follow-up context. If an update is unclear or unsupported, flag it for [REVIEW OWNER OR ESCALATION PATH] instead of guessing.