phuryn/pm-skills

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/phuryn/pm-skills --skill release-notes

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Release Notes Generator

Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.

Context

You are writing release notes for $ARGUMENTS.

If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.

Instructions

  1. Gather raw material: Read all provided tickets, changelogs, or descriptions. Extract:
  • What changed (feature, improvement, or fix)
  • Who it affects (which user segment)
  • Why it matters (the user benefit)
  1. Categorize changes:
  • New Features: Entirely new capabilities
  • Improvements: Enhancements to existing features
  • Bug Fixes: Issues resolved
  • Breaking Changes: Anything that requires user action (migrations, API changes)
  • Deprecations: Features being sunset
  1. Write each entry following these principles:
  • Lead with the user benefit, not the technical change
  • Use plain language — avoid jargon, internal codenames, or ticket numbers
  • Keep each entry to 1-3 sentences
  • Include visuals or screenshots if the user provides them

Example transformations:

  • Technical: "Implemented Redis caching layer for dashboard API endpoints"
  • User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
  • Technical: "Fixed race condition in concurrent checkout flow"
  • User-facing: "Fixed an issue where some orders could fail during high-traffic periods."
  1. Structure the release notes:
   # [Product Name] — [Version / Date]

   ## New Features
   - **[Feature name]**: [1-2 sentence description of what it does and why it matters]

   ## Improvements
   - **[Area]**: [What got better and how it helps]

   ## Bug Fixes
   - Fixed [issue description in user terms]

   ## Breaking Changes (if any)
   - **Action required**: [What users need to do]
  1. Adjust tone to match the product's voice — professional for B2B, friendly for consumer, developer-focused for APIs.

Save as a markdown document. If the user wants HTML or another format, convert accordingly.

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
phuryn
社区

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1小时安装量
4
GitHub Stars
2.8万
最近更新
11月8日
phuryn
社区

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1小时安装量
2
GitHub Stars
2.8万
最近更新
11月8日
phuryn
社区

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1小时安装量
2
GitHub Stars
2.8万
最近更新
11月8日
phuryn
社区

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1小时安装量
2
GitHub Stars
2.8万
最近更新
11月8日