Generate Shipped Changelog From Sprint Tasks

Product and engineering teams writing customer-facing changelogs often rely on task status alone, which overstates what actually shipped and buries customers in duplicate, engineering-worded entries. This workflow gives PMs a changelog that is provably accurate before it gets published.

1. Matches every completed sprint task to its linked GitHub pull request and confirms the PR merged to the release branch, not just to main.
2. Classifies verified changes as Feature, Improvement, or Fix, and filters out internal-only work like refactors and tooling changes.
3. Merges tasks that deliver a single customer-visible change into one deduplicated entry, then rewrites it in plain customer language against a fixed voice profile.
4. Routes the draft, plus any unverified or low-confidence entries, to the PM for approval via Chat.
5. Commits the approved changelog to the docs repository as a pull request and verifies the merged diff matches what was approved.
6. Announces the release in company and product channels and updates roadmap epic statuses to reflect what actually shipped.

A publish-ready, customer-facing changelog where every entry traces back to a verified, merged pull request, with duplicate engineering tasks collapsed into single, correctly categorized customer-visible lines, plus roadmap and epic statuses automatically reconciled to match.

• Runs on ClickUp, using Sprints to track task completion and Docs, Chat, Goals, Dashboards, and Automations to draft, route, and announce the changelog
• Connects to GitHub through an MCP integration, with read access to pull requests to verify what merged and write access scoped only to the docs repository to commit the final changelog
• Needs a changelog voice profile Doc and a product glossary set up in advance, so the rewriting step has a consistent style and terminology to follow
• Needs a controlled product area taxonomy defined ahead of time, used to tag and group changelog entries consistently

• Runs on ClickUp, using Sprints to track task completion and Docs, Chat, Goals, Dashboards, and Automations to draft, route, and announce the changelog
• Connects to GitHub through an MCP integration, with read access to pull requests to verify what merged and write access scoped only to the docs repository to commit the final changelog
• Needs a changelog voice profile Doc and a product glossary set up in advance, so the rewriting step has a consistent style and terminology to follow
• Needs a controlled product area taxonomy defined ahead of time, used to tag and group changelog entries consistently