stakeholder-update-generator

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "stakeholder-update-generator" with this command: npx skills add pmprompt/claude-plugin-product-management/pmprompt-claude-plugin-product-management-stakeholder-update-generator

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

prd-writer

No summary provided by upstream source.

Repository SourceNeeds Review
General

feature-prioritization-assistant

No summary provided by upstream source.

Repository SourceNeeds Review
General

thinking-in-bets

No summary provided by upstream source.

Repository SourceNeeds Review