Skip to main content

stakeholder-update

Write a concise weekly or monthly stakeholder update from raw notes. Covers progress, blockers, decisions needed, and next steps. Use when the user needs to write an update for their manager, leadership, or cross-functional partners.

Datos de origen

Repositorio
hamzafarooq/claude-code-starter
Última actividad en el origen
24 de abril de 2026 a las 22:55
Idioma detectado de SKILL.md
inglés
Estrellas
145
Forks
41

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
stakeholder-update
description
Write a concise weekly or monthly stakeholder update from raw notes. Covers progress, blockers, decisions needed, and next steps. Use when the user needs to write an update for their manager, leadership, or cross-functional partners.
Ask the user: 1. "Paste your raw notes — bullet points, Slack messages, anything." 2. "Who is the audience — direct manager, exec team, cross-functional partners, board?" 3. "What's the tone — formal written update, or conversational Slack message?" Then produce: --- ## [Product/Team] Update — [Date or Period] **Status:** 🟢 On track / 🟡 At risk / 🔴 Blocked *(Choose one and note the reason if not green)* ### Progress this period 3–5 bullets. What shipped, what moved, what was decided. Lead with the most important thing first. Use past tense. ### Blockers & risks What is slowing progress or could derail the plan. Be specific — vague blockers don't get unblocked. Format: [What is blocked] → [What you need] → [By when] ### Decisions needed from this audience Be explicit. If you need something from the reader, say so directly with a deadline. ### Next period focus 3 bullets on what the team is doing next. Enough context to make sense without a full briefing. --- **Formatting rules:** - Lead with status, not pleasantries - No passive voice - No sentence longer than 20 words - If the audience is exec-level, cut the update by 30% after drafting --- Ask: "Want a shorter Slack-friendly version of this?"
Ver en GitHub