{"id":"0d46cf74-5cc7-418b-8701-49a6705a52cf","shortId":"gUW6Sx","kind":"skill","title":"stakeholder-brief","tagline":"Write exec-ready stakeholder updates, decision documents, and status reports. Adapts tone and detail level for different audiences (exec team, engineering, cross-functional). Structured for fast decision-making.","description":"# Stakeholder Brief Skill\n\nGenerate polished stakeholder communications — status updates, decision docs, and executive briefs.\n\n## When to Use\n- User needs to write a status update for leadership\n- User needs a decision document for a cross-functional review\n- User needs to communicate product changes to stakeholders\n- User says `/stakeholder-brief` followed by the context\n- Any exec communication that needs to be clear, concise, and actionable\n\n## Document Types\n\n### Type 1: Status Update\nFor regular cadence updates (weekly, monthly, quarterly).\n\n**Structure:**\n1. **TL;DR** (2-3 sentences): What happened, what's next, any blockers\n2. **Key Metrics**: Table of 3-5 metrics with trend arrows (up/down/flat)\n3. **Highlights**: Top 2-3 wins this period\n4. **Lowlights**: Top 1-2 challenges or misses\n5. **Next Period Focus**: What the team will prioritize\n6. **Asks**: What you need from the audience (decisions, resources, alignment)\n\n### Type 2: Decision Document\nFor getting alignment on a specific decision.\n\n**Structure:**\n1. **Decision Needed**: One sentence stating the decision clearly\n2. **Deadline**: When this decision is needed by (and why)\n3. **Context**: 2-3 paragraphs of background (assume the reader has limited context)\n4. **Options** (3 max):\n   | | Option A | Option B | Option C |\n   |---|---|---|---|\n   | Description | | | |\n   | Pros | | | |\n   | Cons | | | |\n   | Effort | | | |\n   | Risk | | | |\n5. **Recommendation**: Which option and why (be opinionated)\n6. **What Happens If We Don't Decide**: The cost of inaction\n7. **Appendix**: Supporting data, research, or analysis\n\n### Type 3: Executive Brief\nFor escalations, board updates, or senior leadership.\n\n**Structure:**\n1. **Bottom Line Up Front (BLUF)**: One sentence conclusion/ask\n2. **Situation**: What's happening (facts only, 2-3 sentences)\n3. **Complication**: Why this matters / what changed (2-3 sentences)\n4. **Resolution**: What you propose (specific action items with owners and dates)\n5. **Supporting Data**: Key numbers in a table or bullet list\n6. **Risks**: What could go wrong with the proposed resolution\n\n## Audience Adaptation\n\nAdjust detail level and language based on audience:\n\n**C-Suite / Board:**\n- Maximum 1 page\n- Focus on business impact and strategic implications\n- Use revenue, user growth, competitive positioning language\n- Include specific asks with dollar amounts or headcount\n\n**VP / Director:**\n- 1-2 pages\n- Include metrics AND qualitative context\n- Reference OKR/goal alignment\n- Include timeline and dependencies\n\n**Engineering / Cross-Functional:**\n- Can be longer\n- Include technical details where relevant\n- Use specific feature/project names\n- Include clear ownership and next steps\n\n## Writing Principles\n- **Lead with the ask**: Don't bury the lead. What do you need?\n- **Be specific**: \"Revenue up 12% QoQ\" not \"Revenue is trending well\"\n- **Show your work**: Link to data sources, include methodology\n- **Anticipate questions**: Address the obvious follow-ups preemptively\n- **Use formatting**: Tables, bold, bullet points — make it scannable\n- **State confidence**: \"We're 80% confident\" is more useful than \"We think\"\n\n## Output Format\nGenerate clean markdown optimized for pasting into email, Slack, Notion, or Google Docs. Use tables for comparisons. Bold key numbers. Keep paragraphs short (2-3 sentences max).","tags":["stakeholder","brief","skills","aroyburman-codes","agent-skills","claude-code","claude-skills","frameworks","metrics","pm-tools","product-management","product-strategy"],"capabilities":["skill","source-aroyburman-codes","skill-stakeholder-brief","topic-agent-skills","topic-claude-code","topic-claude-skills","topic-frameworks","topic-metrics","topic-pm-tools","topic-product-management","topic-product-strategy"],"categories":["pm-skills"],"synonyms":[],"warnings":[],"endpointUrl":"https://skills.sh/aroyburman-codes/pm-skills/stakeholder-brief","protocol":"skill","transport":"skills-sh","auth":{"type":"none","details":{"cli":"npx skills add aroyburman-codes/pm-skills","source_repo":"https://github.com/aroyburman-codes/pm-skills","install_from":"skills.sh"}},"qualityScore":"0.453","qualityRationale":"deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 6 github stars · SKILL.md body (3,346 chars)","verified":false,"liveness":"unknown","lastLivenessCheck":null,"agentReviews":{"count":0,"score_avg":null,"cost_usd_avg":null,"success_rate":null,"latency_p50_ms":null,"narrative_summary":null,"summary_updated_at":null},"enrichmentModel":"deterministic:skill-github:v1","enrichmentVersion":1,"enrichedAt":"2026-05-18T19:14:48.087Z","embedding":null,"createdAt":"2026-05-18T13:22:17.331Z","updatedAt":"2026-05-18T19:14:48.087Z","lastSeenAt":"2026-05-18T19:14:48.087Z","tsv":"'-2':149,375 '-3':116,141,207,288,298,502 '-5':131 '/stakeholder-brief':82 '1':101,112,148,185,271,348,374 '12':430 '2':115,125,140,174,194,206,280,287,297,501 '3':130,137,204,219,260,290 '4':145,217,300 '5':153,232,312 '6':162,240,323 '7':252 '80':468 'action':97,306 'adapt':15,334 'address':448 'adjust':335 'align':172,179,384 'amount':369 'analysi':258 'anticip':446 'appendix':253 'arrow':135 'ask':163,366,416 'assum':211 'audienc':22,169,333,342 'b':224 'background':210 'base':340 'blocker':124 'bluf':276 'board':265,346 'bold':458,495 'bottom':272 'brief':3,36,48,262 'bullet':321,459 'buri':419 'busi':352 'c':226,344 'c-suit':343 'cadenc':106 'challeng':150 'chang':77,296 'clean':479 'clear':94,193,406 'communic':41,75,89 'comparison':494 'competit':361 'complic':291 'con':229 'concis':95 'conclusion/ask':279 'confid':465,469 'context':86,205,216,381 'cost':249 'could':326 'cross':27,69,391 'cross-funct':26,68,390 'data':255,314,442 'date':311 'deadlin':195 'decid':247 'decis':10,33,44,64,170,175,183,186,192,198 'decision-mak':32 'depend':388 'descript':227 'detail':18,336,398 'differ':21 'director':373 'doc':45,490 'document':11,65,98,176 'dollar':368 'dr':114 'effort':230 'email':485 'engin':25,389 'escal':264 'exec':6,23,88 'exec-readi':5 'execut':47,261 'fact':285 'fast':31 'feature/project':403 'focus':156,350 'follow':83,452 'follow-up':451 'format':456,477 'front':275 'function':28,70,392 'generat':38,478 'get':178 'go':327 'googl':489 'growth':360 'happen':119,242,284 'headcount':371 'highlight':138 'impact':353 'implic':356 'inact':251 'includ':364,377,385,396,405,444 'item':307 'keep':498 'key':126,315,496 'languag':339,363 'lead':413,421 'leadership':60,269 'level':19,337 'limit':215 'line':273 'link':440 'list':322 'longer':395 'lowlight':146 'make':34,461 'markdown':480 'matter':294 'max':220,504 'maximum':347 'methodolog':445 'metric':127,132,378 'miss':152 'month':109 'name':404 'need':53,62,73,91,166,187,200,425 'next':122,154,409 'notion':487 'number':316,497 'obvious':450 'okr/goal':383 'one':188,277 'opinion':239 'optim':481 'option':218,221,223,225,235 'output':476 'owner':309 'ownership':407 'page':349,376 'paragraph':208,499 'past':483 'period':144,155 'point':460 'polish':39 'posit':362 'preemptiv':454 'principl':412 'priorit':161 'product':76 'propos':304,331 'pros':228 'qoq':431 'qualit':380 'quarter':110 'question':447 're':467 'reader':213 'readi':7 'recommend':233 'refer':382 'regular':105 'relev':400 'report':14 'research':256 'resolut':301,332 'resourc':171 'revenu':358,428,433 'review':71 'risk':231,324 'say':81 'scannabl':463 'senior':268 'sentenc':117,189,278,289,299,503 'short':500 'show':437 'situat':281 'skill':37 'skill-stakeholder-brief' 'slack':486 'sourc':443 'source-aroyburman-codes' 'specif':182,305,365,402,427 'stakehold':2,8,35,40,79 'stakeholder-brief':1 'state':190,464 'status':13,42,57,102 'step':410 'strateg':355 'structur':29,111,184,270 'suit':345 'support':254,313 'tabl':128,319,457,492 'team':24,159 'technic':397 'think':475 'timelin':386 'tl':113 'tone':16 'top':139,147 'topic-agent-skills' 'topic-claude-code' 'topic-claude-skills' 'topic-frameworks' 'topic-metrics' 'topic-pm-tools' 'topic-product-management' 'topic-product-strategy' 'trend':134,435 'type':99,100,173,259 'up':453 'up/down/flat':136 'updat':9,43,58,103,107,266 'use':51,357,401,455,472,491 'user':52,61,72,80,359 'vp':372 'week':108 'well':436 'win':142 'work':439 'write':4,55,411 'wrong':328","prices":[{"id":"1d7123bd-97cc-4a63-9e33-e305450aff34","listingId":"0d46cf74-5cc7-418b-8701-49a6705a52cf","amountUsd":"0","unit":"free","nativeCurrency":null,"nativeAmount":null,"chain":null,"payTo":null,"paymentMethod":"skill-free","isPrimary":true,"details":{"org":"aroyburman-codes","category":"pm-skills","install_from":"skills.sh"},"createdAt":"2026-05-18T13:22:17.331Z"}],"sources":[{"listingId":"0d46cf74-5cc7-418b-8701-49a6705a52cf","source":"github","sourceId":"aroyburman-codes/pm-skills/stakeholder-brief","sourceUrl":"https://github.com/aroyburman-codes/pm-skills/tree/main/skills/stakeholder-brief","isPrimary":false,"firstSeenAt":"2026-05-18T13:22:17.331Z","lastSeenAt":"2026-05-18T19:14:48.087Z"}],"details":{"listingId":"0d46cf74-5cc7-418b-8701-49a6705a52cf","quickStartSnippet":null,"exampleRequest":null,"exampleResponse":null,"schema":null,"openapiUrl":null,"agentsTxtUrl":null,"citations":[],"useCases":[],"bestFor":[],"notFor":[],"kindDetails":{"org":"aroyburman-codes","slug":"stakeholder-brief","github":{"repo":"aroyburman-codes/pm-skills","stars":6,"topics":["agent-skills","ai","claude-code","claude-skills","frameworks","metrics","pm-tools","product-management","product-strategy"],"license":"mit","html_url":"https://github.com/aroyburman-codes/pm-skills","pushed_at":"2026-02-17T06:52:03Z","description":"PM workflow and product thinking skills for AI product managers. 17 structured frameworks for PRDs, metrics, strategy, writing, prioritization, and more.","skill_md_sha":"32593de7f0afa3e73edf666339e14c85418d78ec","skill_md_path":"skills/stakeholder-brief/SKILL.md","default_branch":"main","skill_tree_url":"https://github.com/aroyburman-codes/pm-skills/tree/main/skills/stakeholder-brief"},"layout":"multi","source":"github","category":"pm-skills","frontmatter":{"name":"stakeholder-brief","description":"Write exec-ready stakeholder updates, decision documents, and status reports. Adapts tone and detail level for different audiences (exec team, engineering, cross-functional). Structured for fast decision-making."},"skills_sh_url":"https://skills.sh/aroyburman-codes/pm-skills/stakeholder-brief"},"updatedAt":"2026-05-18T19:14:48.087Z"}}