stakeholder-update

Convert raw notes into structured stakeholder updates for email, Slack, or decks.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill stakeholder-update-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-update
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/09-product-management/stakeholder-update
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill stakeholder-update-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scattered meeting notes, Slack threads, and status updates are hard to turn into a clear stakeholder communication. This Skill synthesizes messy raw input into a concise, structured update with a TL;DR, progress, blockers, and decision asks. ## Core Features & Use Cases - Multi-format output: Generates updates as email (default), Slack message, or deck bullet points, each with appropriate tone and length limits. - Structured synthesis: Categorizes raw input into progress, blockers with specific asks, decisions needed with deadlines, and upcoming priorities. - Quantification enforcement: Replaces vague statements with specific numbers, dates, and counts so updates are actionable. - Use Case: Paste a week of sprint notes and Slack threads, and receive a polished under-200-word email update with a two-sentence TL;DR and clearly framed decisions for leadership. ## Quick Start Paste your raw meeting notes or status updates and ask for a stakeholder update in email, Slack, or deck format.

Frequently Asked Questions about stakeholder-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a stakeholder update from messy meeting notes?

Paste your raw notes and the Skill categorizes them into progress, blockers, decisions needed, and next priorities. It then produces a structured update with a two-sentence TL;DR in your chosen format: email, Slack, or deck bullets.

What format should I use for a stakeholder status update?

Email is the default and works for formal weekly updates under 200 words. Use Slack format for quick team check-ins under 100 words, or deck bullets under 50 words for executive presentations.

Can I generate a Slack status update instead of an email?

Yes, request the Slack format explicitly and the output switches to a compact structure with Shipped, Blocked, and Need from you sections. It stays under 100 words with the same TL;DR-first approach.

What happens if my notes are too thin for a status update?

The Skill tells you the input is insufficient and asks for more context rather than padding the update. It synthesizes only what is present in the raw notes and does not invent progress or opinions.

How are blockers handled in a stakeholder update?

Each blocker must include what is stuck, what specific help is needed, and from whom. A blocker without a concrete ask is rewritten or flagged, since complaints without requests are not actionable.