Compile changelogs from merged PRs
Engineers write code. They do not write marketing copy about their code. Every release cycle ends with a product manager or DevRel lead chasing down contributors, reading commit messages, and piecing together what actually shipped. The result is either late documentation or vague bullet points that help nobody. The Release Notes Writer eliminates this manual compilation by reading the actual work record and producing structured notes automatically.
How the Release Notes Writer works
The agent scans your ClickUp workspace for tasks, PRs, and issues resolved since the last tagged release. It groups changes into categories: new features, improvements, bug fixes, deprecations, and breaking changes. For each entry, it writes two versions: a technical summary referencing the specific code change and a user facing description explaining what changed from the customer's perspective. The output follows your team's changelog format (Keep a Changelog, custom templates, or Markdown conventions) and posts as a ClickUp doc ready for review.
Why you need the Release Notes Writer
This agent serves engineering teams shipping on a regular cadence (weekly, biweekly, or per sprint) where manual changelog assembly adds 2 or more hours to every release cycle. Product managers who need to communicate shipped changes to customers, sales, and support without deep technical context benefit from the user facing translation. Teams managing multiple microservices where changes span repositories get particular value from the cross workspace aggregation.
How the Release Notes Writer compares
The Release Notes Writer compiles complete changelogs from the full scope of a release, pulling from multiple sources and categorizing automatically. The Release Note Drafter focuses on writing polished prose for individual features or changes that need more narrative depth. Use both when a release includes a headline feature that deserves a deeper writeup alongside the standard changelog.
