Deliver Release Notes
- 507 installs
- 518 repo stars
- Updated August 4, 2026
- product-on-purpose/pm-skills
deliver-release-notes is a Claude Code skill from product-on-purpose/pm-skills that drafts user-facing release notes and changelog entries from shipped features so developers can communicate version changes clearly to cu
About
deliver-release-notes is a product-management agent skill in the product-on-purpose/pm-skills repository focused on productivity and planning around software releases. Developers and technical PMs reach for deliver-release-notes when a version tag, GitHub release, or app update needs customer-readable notes instead of raw commit logs. The skill transforms merged features, bug fixes, and breaking changes into structured release communication suitable for changelogs, in-app what's-new modals, or email announcements. With minimal manifest detail in the repository, the skill is categorized as a release-communication helper invoked when teams need polished notes at ship time rather than during initial feature design.
- deliver-release-notes
- Productivity & Planning
- AI-coding skill
Deliver Release Notes by the numbers
- 507 all-time installs (skills.sh)
- +26 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #759 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/product-on-purpose/pm-skills --skill deliver-release-notesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 507 |
|---|---|
| repo stars | ★ 518 |
| Last updated | August 4, 2026 |
| Repository | product-on-purpose/pm-skills ↗ |
How do you write release notes from commits?
Helps with productivity & planning tasks.
Who is it for?
Developers or technical PMs publishing a versioned release who need readable changelog copy instead of raw git history.
Skip if: Teams with automated changelog generators already wired into CI that require no manual narrative editing.
When should I use this skill?
The user asks to write, draft, or deliver release notes, changelogs, or what's-new content for an upcoming software release.
What you get
Structured release notes, changelog sections, and user-facing what's-new copy ready for GitHub Releases or product announcements.
- Release notes draft
- Changelog sections
- What's-new announcement copy
Files
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Release Notes
Release notes communicate product changes to users in a way that highlights value and builds excitement. Unlike changelogs (which document what changed technically), release notes translate changes into user benefits. Good release notes help users discover new capabilities, understand improvements, and trust that issues are being addressed.
When to Use
- Shipping product updates to customers
- Communicating changes to internal stakeholders
- Preparing app store update descriptions
- Writing customer-facing email announcements
- Documenting changes for support and sales teams
When NOT to Use
- You are updating internal stakeholders on progress rather than announcing shipped changes -> use
foundation-stakeholder-update - You need the technical record of changes for developers -> keep the engineering changelog; this skill translates changes into user benefits
- You are coordinating launch readiness rather than communicating the ship -> use
deliver-launch-checklist - Nothing user-visible shipped (a pure internal refactor): release notes that stretch to find a benefit erode trust; skip the cycle or fold it into the next one
Instructions
When asked to create release notes, follow these steps:
1. Gather the Changelog Collect all changes included in this release: features, improvements, and bug fixes. Work from engineering changelogs, completed tickets, or pull request descriptions.
2. Identify the Highlights Select 1-3 changes that deserve top billing. These should be changes users will notice and care about most. Lead with the most impactful change.
3. Translate to Benefits Rewrite each change in terms of user value. Instead of "Added pagination to search results," write "Find what you need faster with improved search that handles large result sets." Focus on what users can now do or what's now better.
4. Categorize Changes Group remaining changes into clear categories: New Features, Improvements, and Bug Fixes. Within each category, order by impact (most valuable first).
5. Write Scannable Descriptions Each item should be 1-2 sentences. Lead with the benefit, optionally followed by the "how." Users scan release notes - make each line valuable.
6. Acknowledge Known Issues If there are known limitations or issues, be transparent. Users appreciate honesty, and it reduces support burden.
7. Tease Coming Soon (Optional) If appropriate, hint at what's coming next. This builds anticipation and shows momentum, but don't over-promise.
Output Format
Use the template in references/TEMPLATE.md to structure the output. Complete release notes fill the template sections: Highlights; New Features; Improvements; Bug Fixes; Known Issues; Coming Soon (optional); and Feedback.
Quality Checklist
Before finalizing, verify:
- [ ] Highlights feature the 1-3 most impactful changes
- [ ] Each item leads with user benefit, not technical description
- [ ] Language is jargon-free and accessible to all users
- [ ] Items are concise (1-2 sentences each)
- [ ] Bug fixes mention the problem that was solved
- [ ] No internal jargon, ticket IDs, or code names leak through; every line reads as customer-facing
Examples
See references/EXAMPLE.md for a completed example.
Scenario: consumer fintech app v4.0 release notes from a messy changelog (leak + breaking-change traps)
This is the INPUT brief for an output-quality eval. The skill arm and the control arm each receive everything below (and nothing else about how to do the work) and produce user-facing release notes for it. Judges never see this header. The raw changelog is deliberately jargon-heavy and seeded with traps: a breaking change users must act on, a security fix that needs careful non-alarming wording, regional and tier eligibility, and internal code names / ticket IDs that must NOT leak. A quick freehand pass tends to restate the changelog (leaking jargon, burying the breaking change, mishandling the security note); the skill should win decisively on benefit-led translation, no-leak, and surfacing the required user action.
Product
A consumer personal-finance app ("Plume"). Audience for the notes: everyday non-technical users, shown in-app and in the app-store description.
Engineering changelog for v4.0 (raw)
Features (project "Atlas"):
- ATL-410: Shipped the new
goals_v2service - users can create multiple savings goals with auto-transfer
rules. Behind the goals_multi flag at 100% for US/CA; EU rollout pending DPA sign-off (~2 weeks out).
- ATL-433: Added "Smart Categories" using the new categorization model
catmodel-3. Premium tier only.
Breaking change:
- ATL-450: Removed the legacy CSV export (
/export/v1). Users MUST migrate to the new "Statements"
export. Any saved automations pointing at the old export will stop working on update. Scheduled-export users need to re-create their export in Settings > Statements.
Improvements:
- PERF-
102: Cut p95 transaction-list render from 1.8s to 0.6s by virtualizing the list. - SYNC-77: Switched bank sync from
aggregator-Atoaggregator-B; one-time re-link required for ~4% of
users whose institution moved providers (affected users get an in-app prompt).
Security fix:
- SEC-318: Patched a session-token rotation bug (CVE pending) where tokens were not invalidated on
password change. No evidence of exploitation. Users do not need to do anything, but security wants this communicated without alarming language.
Bug fixes:
- BUG-2207: Fixed incorrect available-balance for
pending_authholds on debit accounts. - BUG-2231: Fixed a crash on iOS 17 when opening a goal with an emoji in its name.
Known issue:
- Smart Categories occasionally mislabels peer-to-peer transfers; fix in
catmodel-3.1next release.
What the team wants
Clear, benefit-led, jargon-free notes a user will actually read, with the most impactful changes highlighted, the breaking change and its required user action unmissable, the security fix communicated calmly and accurately, eligibility (tier/region/affected-subset) stated where relevant, and zero internal code names, ticket IDs, or technical framing leaking through. The audience is end users, not developers.
Scenario: mobile app v3.2 release notes from an engineering changelog
This is the INPUT brief for an output-quality eval. The skill arm and the control arm each receive everything below (and nothing else about how to do the work) and produce user-facing release notes for it. Judges never see this header. The input is the RAW engineering changelog (jargon, ticket IDs, and code names on purpose); the skill's job is to translate it for users.
Product
A consumer personal-finance mobile app ("MoneyMap"). The audience for the release notes is everyday users (non-technical), shown in-app and in the app-store update description.
Engineering changelog for v3.2 (raw)
Features (project "Lighthouse"):
- LH-204: Implemented shared budgets ("Spaces") so multiple users can co-manage a budget. Backend
multi-tenant ACL added.
- LH-231: Added biometric unlock (FaceID/TouchID) gated behind the
secure_unlockfeature flag. - LH-240: New "Insights" tab surfacing month-over-month category spend deltas via the new
aggregation service.
Improvements:
- PERF-77: Reduced cold-start time ~40% by lazy-loading the transactions module.
- LH-256: Migrated charts from the deprecated
ChartKitV1toChartKitV2; smoother rendering. - ACCT-12: Account-sync now retries on transient bank-API 5xx errors instead of failing silently.
Bug fixes:
- BUG-1187: Fixed a crash on Android 14 when opening a transaction with an emoji in the note field.
- BUG-1201: Fixed duplicate-transaction display when two devices synced within the same minute.
- BUG-1190: Fixed incorrect currency symbol for users with a GBP account but a US locale.
Known issue:
- Recurring-transaction detection (
recurring_v2) is still behind a flag for ~10% of users; full
rollout next release.
What the team wants
Clear, benefit-led, jargon-free release notes a user will actually read, with the most impactful changes highlighted. The audience is end users, not developers.
{
"schema": 1,
"skill": "deliver-release-notes",
"runs_per_query": 3,
"trigger_threshold": 0.5,
"queries": [
{
"q": "Write release notes for version 4.2: we shipped dark mode, faster search, and fixed the export bug",
"expect": "trigger",
"split": "train"
},
{
"q": "Turn this changelog of merged PRs into something customers will actually want to read",
"expect": "trigger",
"split": "train",
"notes": "No 'release notes' keyword; benefit-translation intent"
},
{
"q": "We're shipping the spring update on Friday; draft the what's-new announcement for the in-app banner and email",
"expect": "trigger",
"split": "train"
},
{
"q": "Prepare the app store update description for the new iOS build",
"expect": "trigger",
"split": "train"
},
{
"q": "Support and sales keep getting surprised by what we ship; write the customer-facing summary of this release for them",
"expect": "trigger",
"split": "train"
},
{
"q": "Translate these engineering ticket titles into benefit-focused notes users can understand for the monthly product update",
"expect": "trigger",
"split": "train"
},
{
"q": "Draft release notes for the Q2 platform update, highlighting the three biggest features",
"expect": "trigger",
"split": "validation"
},
{
"q": "Our users have no idea we fixed the sync issue they kept complaining about; announce this release in a way that rebuilds trust",
"expect": "trigger",
"split": "validation",
"notes": "Intent-only ask, no artifact keyword"
},
{
"q": "Write the customer email announcing the new integrations we shipped this sprint",
"expect": "trigger",
"split": "validation"
},
{
"q": "Summarize this release for customers: new SSO support, two performance improvements, five bug fixes, all in user-benefit language",
"expect": "trigger",
"split": "validation"
},
{
"q": "The release is in two weeks; build the checklist that makes sure marketing, support, and legal are ready for it",
"expect": "no-trigger",
"split": "train",
"near_miss_of": "deliver-launch-checklist",
"notes": "Coordinating launch readiness, not communicating the ship, per When NOT to Use"
},
{
"q": "Send leadership the weekly progress update on the migration project; nothing has shipped yet",
"expect": "no-trigger",
"split": "validation",
"near_miss_of": "foundation-stakeholder-update",
"notes": "Progress update to internal stakeholders, not an announcement of shipped changes"
},
{
"q": "Generate a technical changelog from these commit messages for the developer docs",
"expect": "no-trigger",
"split": "train",
"notes": "Engineering-facing record; the skill's boundary keeps the changelog separate"
},
{
"q": "Write user stories for the notification preferences feature",
"expect": "no-trigger",
"split": "train"
},
{
"q": "Nothing user-visible shipped this cycle, it was all refactoring; write a retrospective on the refactor work instead",
"expect": "no-trigger",
"split": "validation",
"notes": "The skill's own boundary says skip the cycle when nothing user-visible shipped"
},
{
"q": "Draft the PRD for the upcoming billing revamp",
"expect": "no-trigger",
"split": "train"
},
{
"q": "Fix this TypeError in my React component when the props are undefined",
"expect": "no-trigger",
"split": "train",
"notes": "Unrelated debugging ask"
},
{
"q": "Write a SQL query to count weekly active users by cohort",
"expect": "no-trigger",
"split": "validation",
"notes": "Unrelated technical ask"
},
{
"q": "What restaurants should I book for a client dinner in Chicago?",
"expect": "no-trigger",
"split": "train",
"notes": "Unrelated logistics ask"
},
{
"q": "Create a competitive analysis of the top three release-management tools",
"expect": "no-trigger",
"split": "validation",
"notes": "Contains 'release' but is a discover-phase research ask"
}
]
}
deliver-release-notes - Version History
| Version | Date | Release | Effort | Type | Summary |
|---|---|---|---|---|---|
| 2.1.0 | 2026-06-10 | v2.26.0 | F-12-batch-1 | minor | Quality convergence: When NOT to Use + output-contract enumeration (F-12 Batch 1) |
| 2.0.0 | 2026-01-26 | - | - | baseline | Prior published version |
2.1.0 (2026-06-10)
Quality-convergence minor (F-12 Batch 1): added a "When NOT to Use" section with boundary pointers to neighboring skills, and the Output Format now enumerates the template sections a complete artifact fills. No template or example changes.
2.0.0 (2026-01-26)
Baseline row for the prior published version; see git history for its changes.
TaskFlow 3.4
Release Date: January 14, 2026
Highlights
See Your Projects at a Glance with Gantt Charts
Plan and track projects visually with our new Gantt chart view. See task dependencies, identify bottlenecks, and adjust timelines by simply dragging tasks on the timeline. Whether you're managing a product launch or a construction project, Gantt charts help you keep everything on track.
Dark Mode for Late-Night Productivity
Work comfortably in low-light environments with full dark mode support. Your eyes will thank you during those evening planning sessions. Toggle dark mode in Settings, or let it follow your system preferences automatically.
---
New Features
- Export to PDF: Share professional project reports with stakeholders who don't use TaskFlow. Export any project view - including Gantt charts - as a formatted PDF with your company logo.
- Keyboard Shortcuts: Power users, rejoice. Navigate TaskFlow without touching your mouse. Press
?anywhere to see the full shortcut list, or useCmd+K(Mac) /Ctrl+K(Windows) to open the command palette.
- Recurring Task Templates: Set up tasks that repeat on a schedule - daily standups, weekly reviews, monthly reports. Create once, and TaskFlow handles the rest.
Improvements
- Faster Page Loads: We've optimized how projects load, resulting in 40% faster page loads for large projects with 500+ tasks. Complex projects now feel snappy.
- Smarter Search: Search now includes task comments and attachments, not just task titles. Find that discussion from last month without remembering which task it was on.
- Improved Mobile Navigation: The bottom navigation bar now shows your most-used views first, based on your actual usage patterns. Get to what matters faster on mobile.
- Clearer Due Date Warnings: Tasks due today show a yellow indicator; overdue tasks show red. No more missing deadlines because they blended into the background.
Bug Fixes
- Fixed an issue where calendar sync with Outlook 365 would occasionally fail for users with many calendars. All your meetings now sync reliably.
- Fixed an issue where copying a task would not copy its attachments. Duplicated tasks now include all files.
- Fixed an issue where notification emails would sometimes arrive hours late. Notifications now deliver within minutes.
- Fixed an issue where the mobile app would crash when viewing projects with special characters in the name. International project names are now fully supported.
- Fixed an issue where undoing a task deletion would not restore the task's comments. Undo now restores everything.
Known Issues
- Gantt chart export to PDF currently limits charts to 50 visible tasks. For larger projects, try filtering to a specific milestone before exporting. We're working on supporting larger exports.
- Dark mode does not yet apply to email notifications. This is coming in a future update.
---
Coming Soon
We're putting the finishing touches on AI-powered task suggestions - TaskFlow will learn from your completed projects and suggest task breakdowns for new projects. Plus, time tracking is in beta testing and launching next month.
---
Feedback
Love the new Gantt charts? Have ideas for making TaskFlow even better? We'd love to hear from you at feedback@taskflow.app or in the #product-feedback channel in our community.
[Product Name] [Version Number]
Release Date: [Month Day, Year]
Highlights
<!-- 1-3 most impactful changes. These get the most prominent placement. -->
[Highlight 1 Title]
[2-3 sentences describing what's new and why it matters to users. Focus on the benefit and how it improves their experience.]
[Highlight 2 Title]
[2-3 sentences describing what's new and why it matters to users.]
---
New Features
<!-- Features users couldn't do before. Lead with benefit. -->
- [Feature Name]: [Benefit-focused description of what users can now do]
- [Feature Name]: [Benefit-focused description of what users can now do]
Improvements
<!-- Enhancements to existing features. Emphasize what's better. -->
- [Improvement Area]: [What's now better and how it helps users]
- [Improvement Area]: [What's now better and how it helps users]
- [Improvement Area]: [What's now better and how it helps users]
Bug Fixes
<!-- Issues that were resolved. Mention the problem that's now fixed. -->
- Fixed an issue where [problem users experienced]
- Fixed an issue where [problem users experienced]
- Fixed an issue where [problem users experienced]
Known Issues
<!-- Transparency about current limitations. Optional section. -->
- [Issue description and workaround if available]
---
Coming Soon
<!-- Optional teaser for future releases. Don't over-promise. -->
We're working on [brief teaser of upcoming features]. Stay tuned for more updates.
---
Feedback
Have thoughts on this release? [Feedback channel or contact method]
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What does the deliver-release-notes skill produce?
deliver-release-notes produces structured release notes and changelog copy from shipped work, organizing features, fixes, and breaking changes into customer-readable text suitable for GitHub Releases, in-app what's-new screens, or email announcements.
When should developers use deliver-release-notes?
Developers should use deliver-release-notes at ship time when a tagged release needs polished user-facing notes instead of raw commit messages. The skill fits technical PMs preparing launch communication alongside version deployments.