pmprompt/claude-plugin-product-management

stakeholder-update-generator

Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.

First seen Feb 15, 2026

Installation

$ npx skills add pmprompt/claude-plugin-product-management --skill stakeholder-update-generator

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pmprompt/claude-plugin-product-management · top by installs.

npx skills add pmprompt/claude-plugin-product-management

Browse all from pmprompt/claude-plugin-product-management

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 49
License LICENSE
Default branch main
Open issues 2
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,393 B
  • docs SUMMARY.md 167 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 335 installs

SKILL.md

Domain Context

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Input Requirements

  • Context about your product, feature, or problem
  • Relevant data, research, or constraints (recommended but optional)
  • Clear articulation of what you're trying to achieve

Stakeholder Update Generator

When to Use

  • Shipping a new feature or product update
  • Need to communicate progress to stakeholders
  • Writing release notes for users
  • Preparing status updates for leadership
  • Documenting what changed in a sprint or milestone

What This Skill Does

Creates engaging, well-structured updates that communicate what shipped, why it matters, and what comes next.

Instructions

Help me write an engaging update for [product/feature/sprint] that is both informative and compelling. Include:

  1. High-level summary (2-3 sentences)
  2. Key accomplishments or new features

- Feature/item name - Brief description - User benefit and impact

  1. Improvements and fixes
  2. Metrics or results (if available)
  3. What's next

Style preference: [Professional/Casual/Technical] Audience: [Users/Leadership/Engineering/Investors]

Changes to document: [List what shipped, improvements made, or progress achieved]

Best Practices

  • Lead with the most impactful changes
  • Focus on user benefits, not technical details (unless technical audience)
  • Use concrete metrics when possible ("50% faster" not "performance improvements")
  • Keep the tone consistent with your brand
  • Include visuals or screenshots if possible (note them in the text)
  • Add a call-to-action if relevant

Example

Input: Shipped notification center, improved search performance, fixed 15 bugs Output: Structured update highlighting "Never miss an important update" (notification center benefits), "Find anything in seconds" (search improvements), professional tone, metrics included (3x faster search), next steps mentioned

Further Reading