Auto-draft a sales release deck when Linear ships a feature

Build me an agent workflow that auto-drafts a sales-enablement release deck in Google Slides whenever engineering ships a new feature in Linear. The goal is that the morning a feature launches, PMs and AEs already have a four-slide deck waiting on the Linear issue, drafted from the PRD I keep in Notion.

Trigger: a Linear webhook on issue state changes. The agent should only run when an issue tagged release moves into the Done state. Skip everything else.

Steps the agent should follow:

1. Call linear.Get Issue to pull the issue title, description, contributors / assignee, labels, and any linked URLs. Find the Notion page URL on the issue (it is usually pasted into the description or attached as a link).

2. Call notion.Retrieve Page as Markdown on that Notion URL to read the PRD as clean markdown. This is the source of truth for what shipped and why.

3. Create the deck in Google Slides. Default path: call google-slides.Create a Presentation to spin up a fresh deck titled with the feature name. Optional path the user can switch on: if a release-deck template Drive file ID is configured, call google-drive.Copy File first to clone the template, then write into the copy instead of a blank deck.

4. Build out four slides using google-slides.CreateSlide, google-slides.CreateShape (text boxes), and google-slides.InsertText. The four slides the field team actually needs are:

- Slide 1, What Shipped: feature name and a one-line summary in plain English.

- Slide 2, Who It's For: target persona and the primary use case, pulled from the PRD.

- Slide 3, Before vs After: the customer problem on the left, the fix on the right.

- Slide 4, How to Pitch It: three short talking points plus one objection and the response to it.

5. Call linear.Add Comment to Issue to post the Google Slides link back on the original Linear issue so the PM, product marketing, and AEs can grab it in one click.

Tone of the deck copy: confident and concrete, written for AEs and CSMs to read out loud on a customer call. No engineering jargon, no ticket IDs, no internal-only language. If the PRD does not contain enough information to fill a slide (for example, no objection handler is written down), leave a clearly marked placeholder so the PM knows what to fill in instead of hallucinating content.

Edge cases to handle: if the Linear issue has no Notion URL, skip the Notion read and build the deck from just the issue title and description, and flag in the Linear comment that a PRD link would improve future drafts. If the agent cannot find a tag called release, do nothing and exit silently.