HERO

AI product update summarizer

One-line value: Reduce release-note noise by shipping summaries teams can act on in minutes.

When to use: Use this after vendor updates, internal product releases, or weekly changelog reviews.

QUICK RESULT

If you only do one thing → publish a one-page summary with three sections: what changed, who is affected, and what must be done this week.

ACTION CHECKLIST

• [ ] Collect release notes and changelog links into one input doc.
• [ ] Classify each change as critical, watch, or informational.
• [ ] Extract one business impact line per critical/watch item.
• [ ] Assign an owner and due date for each action-required item.
• [ ] Publish the final summary to the team channel with a link to source notes.

EXAMPLE / DEMO

Raw input: 1,800-word vendor changelog with mixed UI tweaks and API deprecations.

Output summary: “2 critical items (API scope change, webhook retry limit), 3 watch items, 5 informational updates — owners assigned for two immediate fixes.”

WHY IT WORKS

• Separates “need action now” from “nice to know.”
• Preserves source traceability so teams trust the summary.
• Adds owners and due dates to prevent passive reading.

NEXT ACTION

• Run this on your latest release note set and post the summary in your weekly ops thread.

Source notes (kept for context)

Workflow

1. collect release notes
2. summarize changes
3. extract highlights
4. distribute summary