release-notes-writer

Generate release notes from specs and tickets by providing the release scope and related documentation to produce categorized, ready-to-publish Markdown. The output separates user-facing sections from internal technical details, reducing manual drafting time.

The best way to structure release notes for product deployments is to categorize changes into What's New, Enhancements, Bug Fixes, and Known Issues. This structured Markdown format separates user-facing communication from internal deployment and migration details.

Yes, you can create both user-facing and internal release notes from the same specs and tickets. The process explicitly separates user-facing feature updates from internal technical changes, deployment notes, and migration details within a single Markdown document.

Yes, the release notes output supports Markdown format for documentation. It produces ready-to-publish Markdown files structured with standard sections for New Features, Enhancements, Bug Fixes, and Known Issues for direct integration into product management workflows.

Categorize bug fixes and new features in maintenance update release notes by sorting changes into distinct sections: What's New, Enhancements, Bug Fixes, and Known Issues. This categorization applies across engineering, product, and operations deployment scopes.