agentleFS
nisarthnisarth/claude-skills-store/skills/product-management/stakeholder-update/SKILL.md

stakeholder-update

Skill1 starsChanged 7 months agoMITView on GitHub

Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing formats. Trigger phrases: "stakeholder update", "status update", "exec update", "write an update for", "weekly update", "monthly update", "project status", "leadership update", "communicate progress", "send an update to", "status email"

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use experiment-designer, launch-readiness and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Dokkabei97Skill

    experiment-designer

    Designs A/B tests and product experiments with hypothesis structuring, sample size calculation, duration estimation, and result interpretation. Unified framework for both product and marketing experiments.

    Also in 3 projects that use this

  • pratikshadakeSkill

    launch-readiness

    Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.

    Also in 3 projects that use this

  • RhyGSkill

    write-prd

    Also in 3 projects that use this

  • OpenAISkill

    market-sizing

    Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.

    Also in 3 projects that use this

  • MetaSkill

    roadmap

    Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.

    Also in 3 projects that use this

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use business language, not technical jargon

    line 44
  2. Distinctive:

    Use precise technical language

    line 51
  3. Distinctive:

    Call out items requiring cross-team coordination

    line 57
  4. Distinctive:

    Avoid internal jargon and team names

    line 61
  5. Distinctive:

    Separate achievements from plans: Do not mix "what we did" with "what we will do." Readers need to know the difference.

    line 173
  6. Distinctive:

    Make asks explicit: If you need something from a stakeholder, state it clearly with a deadline.

    line 175
  7. Distinctive:

    Consistent format: Use the same template every period so readers know where to look for what.

    line 176

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stakeholder Update Generator

Generate stakeholder updates tailored to audience, cadence, and communication purpose. Translate the same information into different formats for executives, engineering teams, and customers.

Workflow

Step 1: Define the Update Parameters

Clarify before writing:

  1. Audience: Who is reading this? (exec, engineering, cross-functional, customer, board)
  2. Cadence: Weekly, monthly, quarterly, or ad-hoc (launch, incident, escalation)?
  3. Channel: Email, Slack, document, presentation slide?
  4. Tone: Standard update, celebration, warning, or escalation?
  5. Content: What happened, what is coming, what is at risk?

Step 2: Gather the Raw Material

Collect from the user:

  • Accomplishments: What shipped, launched, or was decided?
  • Progress: What is in flight and how far along?
  • Metrics: Key numbers that show progress or health.
  • Risks/Blockers: What could delay or derail current plans?
  • Asks: What do you need from stakeholders? (decision, resources, feedback)
  • Next steps: What is coming in the next period?

Step 3: Tailor to Audience

Executive brief (C-suite, VP+):

  • Lead with the bottom line: are we on track, ahead, or behind?
  • Metrics only: skip implementation details
  • Highlight decisions needed and risks
  • 3-5 bullet points maximum
  • Use business language, not technical jargon

Engineering detail (tech leads, eng managers):

  • Include technical specifics and architecture decisions
  • Reference PRs, incidents, and technical debt
  • Detail blockers with specificity
  • Include velocity and capacity data
  • Use precise technical language

Cross-functional (product, design, marketing, sales):

  • Balance detail with accessibility
  • Highlight what matters to each function
  • Include timeline impacts and dependencies
  • Call out items requiring cross-team coordination

Customer-facing (release notes, customer success):

  • Focus on user value, not internal process
  • Avoid internal jargon and team names
  • Frame changes as benefits
  • Include migration steps or breaking changes
  • Set expectations for what is coming

Step 4: Write the Update

Standard Weekly/Monthly Template

## [Team/Project] Update: [Date/Period]

### TL;DR
[1-2 sentences: overall status, biggest highlight, biggest concern]

### Status: [On Track / At Risk / Off Track]

### Highlights
- [Accomplishment 1]: [Impact or result]
- [Accomplishment 2]: [Impact or result]

### In Progress
- [Initiative 1]: [Status, % complete, expected completion]
- [Initiative 2]: [Status, % complete, expected completion]

### Risks & Blockers
- [Risk/Blocker]: [Impact] | [Mitigation/Ask]

### Key Metrics
| Metric | Current | Target | Trend |
|--------|---------|--------|-------|
| [Metric] | [Value] | [Value] | Up/Down/Flat |

### Decisions Needed
- [Decision]: [Context] | Needed by: [Date]

### Next Period
- [Plan 1]
- [Plan 2]

Escalation Template

## Escalation: [Issue Title]

### Severity: [P0/P1/P2]
### Impact: [Who and what is affected]

### Summary
[2-3 sentences: what happened, current state, customer impact]

### Timeline
- [Date/Time]: [Event]
- [Date/Time]: [Event]

### Root Cause
[Known or under investigation]

### Current Mitigation
[What is being done right now]

### Ask
[What you need from the audience: decision, resources, approval]

### Next Update
[When the next update will be sent]

Launch Announcement Template

## Launch: [Feature/Product Name]

### What
[1-2 sentences: what shipped and for whom]

### Why It Matters
[Business impact, user value, strategic significance]

### Key Details
- Available to: [User segment, rollout %]
- Key metrics to watch: [Metrics]
- Known limitations: [What is not included]

### Supporting Materials
- [Docs link]
- [Demo link]
- [FAQ link]

### What's Next
[Follow-up work, iteration plans]

Examples

Example 1: Weekly Exec Update

User: "Write a weekly update for my VP. We shipped the new onboarding flow, churn dropped 0.3pp, and we're blocked on the API migration by the platform team." Response: Lead with status (On Track). Highlight: onboarding shipped, early churn signal is positive. Risk: API migration blocked -- quantify impact on timeline. Ask: VP to unblock with platform team lead. Keep to 5-6 lines.

Example 2: Engineering Update

User: "Update for the engineering org on our infrastructure migration." Response: Include technical detail: which services migrated, performance improvements measured, remaining services and timeline. Detail the technical blockers with specificity. Include test coverage and rollback plan status.

Example 3: Customer-Facing Release Notes

User: "We need to tell customers about the new reporting features." Response: Frame as user benefits: "You can now export reports in PDF format" not "We added PDF export to the reporting service." Include screenshots or examples. Note any changes to existing behavior. Provide a help article link.

Best Practices

  1. Lead with the headline. Stakeholders should get the key message from the first two sentences. Most people will not read past the third paragraph.
  2. Status before detail. Green/yellow/red or on-track/at-risk/off-track signals let readers decide how deeply to read.
  3. Separate achievements from plans. Do not mix "what we did" with "what we will do." Readers need to know the difference.
  4. Quantify everything. "Good progress" is empty. "Completed 7 of 10 planned items, on track for Friday delivery" is informative.
  5. Make asks explicit. If you need something from a stakeholder, state it clearly with a deadline. Do not bury it in a paragraph of context.
  6. Consistent format. Use the same template every period so readers know where to look for what. Consistency builds trust and saves time.
  7. Honest about risks. Surfacing risks early builds credibility. Hiding them until they explode destroys it. A PM who escalates early is trusted; one who surprises is not.
  8. Send on schedule. A late update signals disorganization. Set a recurring reminder and protect time to write it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.