skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
pmprompt/claude-plugin-product-management347 installs

stakeholder-update-generator

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

How do I install this agent skill?

npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill stakeholder-update-generator
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a collection of templates and guidelines for generating stakeholder updates. It contains no code, tool invocations, or network operations, and is entirely safe to use.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

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
  3. Improvements and fixes
  4. Metrics or results (if available)
  5. 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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/pmprompt/claude-plugin-product-management/stakeholder-update-generator">View stakeholder-update-generator on skillZs</a>