agentleFS
Sign inStart free
product-on-purposeproduct-on-purpose/pm-skills/skills/deliver-release-notes/SKILL.md

deliver-release-notes

Skill777 starsChanged 10 months agoApache-2.0View on GitHub

Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked to create release notes, follow these steps:

    line 35
  2. Distinctive:

    If there are known limitations or issues, be transparent.

    line 53
  3. Distinctive:

    If appropriate, hint at what's coming next.

    line 56
  4. Very specific:

    Use the template in references/TEMPLATE.md to structure the output.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free