write-stakeholder-updatelisted

# Stakeholder Update Writer ## When to Use Use this skill when you need to communicate product progress to leadership in a way that is clear, honest, and decision-ready. It adds the most value when: - **Weekly or monthly PM cadence** — recurring leadership updates are time-consuming to write well. This skill produces a consistent, one-page format that gives leaders exactly what they need to stay informed without requiring them to read a sprint report. - **Post-sprint leadership communication** — after each sprint, a well-structured update closes the loop between the team's work and leadership's awareness. Use after `sprint-review` to convert sprint data directly into a stakeholder-ready document. - **Escalation or risk communication** — when something is at risk or blocked, leadership needs to know immediately and clearly. The status signal at the top of this format ensures the message lands, and the Decisions Needed section gives leaders a specific action to take rather than leaving them to infer what you're asking for. ## Input Format The skill accepts a range of inputs, from structured documents to a quick verbal summary. The more concrete the input, the more specific the output. **Sprint review output from `sprint-review`:** ``` Path: ./sprint-review-2026-05-05.md ``` **Release notes (from `write-release-notes`):** ``` Path: ./release-notes-2026-05-05.md ``` **OKR progress (optional but recommended):** ``` KR 1.1: Activation rate — current 28%, target 35%, baselin