How I Built an AI Changelog Generator That Writes Release Notes for Three Different Audience

The Problem Nobody Wants to Own Every team I've been on has the same ritual. Sprint ends. Someone asks: "Can you write up what shipped?" The room goes quiet. Developers don't want to do it because they already wrote PR descriptions. Product managers don't want to do it because they don't understand half the technical changes. And customers? They get either nothing or a wall of jargon. The real pain isn't writing a changelog. It's writing three : Technical changelog for developers — breaking changes, migration notes, API diffs Product changelog for PMs and internal stakeholders — features, UX changes, bugs fixed Customer-facing release notes — polished, non-technical, ready for a blog or newsletter Same PRs. Three completely different documents. Nobody has time for that. Existing Tools Fall Short I looked at what's out there: Release Drafter — Template-based, requires strict PR labeling. One format only. GitHub's native release notes — Auto-generated from PR titles. Bare minimum. semant