Writing release notes sucks. I know this because I've written them badly, avoided them entirely, and watched teammates procrastinate on them until the last possible second. Every release cycle, someone has to context-switch out of deep work to manually parse commits, figure out what actually matters, and write it in a way that makes sense to someone (dev? manager? users?). It's tedious. It kills flow. It shouldn't be this hard. So I built Proseflow . The Problem (or: Why I Started This) Release notes live in this awkward middle ground. Developers need technical accuracy. Users need clarity about what changed and why they should care. Executives want the business impact. Writing one version that satisfies all three? That's basically impossible, so most teams pick one audience and hope for the best. Meanwhile, the source of truth—your Git history—is already there. Commits exist. PRs exist. The information is right there . We just need to translate it.…