Every release deserves a clear internal announcement, and product managers rarely have time to write one. An Orkeste agent reads the release notes in Notion or Confluence, or the issues completed in Linear, and drafts a short announcement for the teams who need it: what changed, who it helps, what to tell customers.
The problem
Sales and support learn about new features from customers. The changelog exists, but it is written for engineers and nobody reads it in full.
How the workflow runs
Runs: When you start it after a release, or every week.
Read what shipped: The agent reads the release notes page in Notion or Confluence, or searches Linear for issues completed this week.
Keep what matters: It keeps the changes customers will notice and leaves out internal work.
Draft the announcement: It writes a short post: what changed, who it helps, what to tell customers.
Approve: The post waits in Validations for the product manager.
Post: The approved announcement is posted to the Slack channels you choose.
With Slack posts behind approval, the announcement goes out only after the product manager approves it.
Who does what
Release writer: Turns release notes into an announcement people read.
Product manager (human): Approves the announcement.
What this workflow does not do
Posts to Slack channels; it does not send direct messages or read replies.
Reads Linear issues and the pages you point it to; it does not read GitHub or your code.