Playbook

Ship release notes from what actually merged

Clone an agent that regroups merged changes by user-facing impact instead of by commit, leads every entry with the benefit, puts breaking changes first with a migration step, and keeps a consistent changelog voice release to release.

What the interview covers

1. 01Map the product areas changes get grouped under
2. 02Identify who reads the changelog and what they need from it
3. 03Capture the changelog voice and the entry format
4. 04Define what counts as breaking and how migrations get documented

Backed by