stakeholder-update-generator
Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.
Works with
---
name: stakeholder-update-generator
description: Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.
license: MIT
---
## 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
- [Stakeholder Update Templates](https://pmprompt.com/blog/stakeholder-update-templates)More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

