Help us improve
Share bugs, ideas, or general feedback.
From playbooks-virtuoso
Drafts concise stakeholder Slack/email updates from project context. Useful for communicating status, blockers, decisions, or release readiness.
npx claudepluginhub krzysztofsurdy/code-virtuoso --plugin agents-virtuosoHow this skill is triggered — by the user, by Claude, or both
Slash command
/playbooks-virtuoso:stakeholder-update-writer [optional: topic or context][optional: topic or context]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write a concise, professional stakeholder update message for Slack or email.
Generates structured stakeholder updates with TL;DR headlines, progress trends, risks, and clear asks for status reports and executive summaries.
Transforms raw notes into polished stakeholder updates for email, Slack, or deck bullets. Structures TL;DR, progress, blockers, decisions needed, and next priorities. Ideal for crisp status reports.
Writes status updates, executive summaries, and project communications tailored to stakeholder roles and seniority levels. Helps structure messaging, manage up, and communicate delays or bad news.
Share bugs, ideas, or general feedback.
Write a concise, professional stakeholder update message for Slack or email.
Understand what the user wants to communicate. The source can be anything:
If the context is about tracked work (epic, sprint, tickets), fetch the relevant data to understand the full picture. If it's about a decision, event, or general update, work from what the user provides.
Before drafting, identify:
If unclear, ask the user briefly before drafting.
Tone: Professional, direct, confident. Not corporate fluff. Written as a real person talking to colleagues.
Structure: Flowing text with minimal formatting. Use bold for section headers only when they add clarity. Avoid:
Content flow:
Key principles:
Expect the user to refine. Common feedback patterns:
When iterating, apply the feedback and present the full updated message. Don't ask clarifying questions unless the feedback is genuinely ambiguous.
Hey - update on [topic].
We've [done what / looked into what / decided what], and here's where we are.
Theme A - what's happening, what needs to happen. Who's on it.
Theme B - what's happening. What we need from [person/team].
Theme C - what's happening.
[Effort/timeline framing]. [Key dependency or ask].
[Where to find details]. [Next checkpoint]. Happy to discuss.
| Situation | Recommended Skill |
|---|---|
| When generating a full project report instead of a message | report-writer |
| When writing a PR description, not a stakeholder message | pr-message-writer |
| When planning sprint goals to reference in the update | scrum |