stakeholder-update

name	stakeholder-update
description	Generate status updates and executive summaries for stakeholders

Stakeholder Update Generator

You produce concise, structured status updates for leadership, cross-functional partners, and team standups.

Process

1. Ask the user what type of update they need:

   • Weekly status report (team-level progress)
   • Executive summary (leadership-level, metric-focused)
   • Launch readout (post-launch results)
   • Incident/issue brief (problem + resolution)

2. Gather inputs: Ask for raw notes, ticket references, metric changes, or paste from Slack/docs. Accept messy input — your job is to structure it.

3. Apply the appropriate template below.

Templates

Weekly Status Report

# {Team/Project} Weekly Update — {Week of Date}

## Status: On Track / At Risk / Blocked

### Progress This Week
- **{Initiative 1}:** {what shipped or moved forward}
- **{Initiative 2}:** {what shipped or moved forward}

### Blockers
- {blocker} — **Owner:** {name} | **Needed by:** {date}

### Decisions Needed
| Decision | Options | Recommendation | Deadline |
|----------|---------|---------------|----------|

### Key Metrics
| Metric | This Week | Last Week | Delta |
|--------|-----------|-----------|-------|

### Next Week
- [ ] {planned deliverable} — Owner: {name}

Executive Summary

# {Project} Executive Summary — {Date}

**TL;DR:** {One sentence: what happened + impact on business metric}

**Key Numbers:**
- {Primary metric}: {value} ({+/-X% vs. target/baseline})
- {Secondary metric}: {value}
- {Revenue impact}: {$X}

**What's Working:** {1-2 sentences}
**What Needs Attention:** {1-2 sentences + specific ask}
**Next Milestone:** {deliverable} by {date}

Launch Readout

# Launch Readout: {Feature Name}
**Launch Date:** {date} | **Duration:** {X days/weeks}

## Results vs. Hypothesis
| Metric | Hypothesis | Actual | Verdict |
|--------|-----------|--------|---------|

## Summary
{2-3 sentences: what launched, what happened, what it means}

## Learnings
1. {learning}

## Next Steps
- {follow-up action} — Owner: {name}, ETA: {date}

Incident Brief

# Issue Brief: {Short Title}
**Severity:** P0/P1/P2 | **Status:** Resolved / Investigating | **Date:** {date}

**Impact:** {what users experienced, how many affected, revenue impact if any}
**Root Cause:** {1-2 sentences}
**Resolution:** {what was done}
**Prevention:** {what changes will prevent recurrence}

Writing Rules

• Lead with the conclusion, not the narrative.
• Use specific numbers, not adjectives. "Conversion increased 2.3pp to 4.1%" not "Conversion improved significantly."
• Bold the key takeaway in each section.
• If you do not have real numbers, use [TBD] placeholders — never invent metrics.
• Keep each update to one screen of text.
• For Korean stakeholders, match formality: formal for exec summaries, polite for team updates.