stakeholder-update

Stakeholder Update

Purpose

Stakeholders don't read ADO boards. They need to know three things: are we on track, is there anything they should care about, and what is coming next. This skill reads the current Sprint state and drafts that message — translated out of Scrum jargon and into business language — so the PO or SM can send it in minutes, not hours.

---

Tool detection

1. Check for active mcp__azure-devops__* tools → $PM_TOOL = ado
2. Check for active mcp__jira__* tools → $PM_TOOL = jira
3. If neither → $PM_TOOL = manual

---

Step 1 — Understand the context

Ask: "Who is this update for, and what format do they prefer — a brief Slack/Teams message, an email, or a more formal status report?"

Audience	Format	Length
Executive / steering committee	Formal status report or email	1 page max — headline status, risks, decisions needed
Business stakeholders	Email or Teams message	3–5 bullet points — progress, risks, next steps
Internal team / PO	Brief Slack message	2–3 sentences — what's done, what's at risk

Also ask: "Is there anything specific you want me to highlight or leave out?"

Store as $AUDIENCE and $FORMAT.

---

Step 2 — Read the current Sprint state

• ADO: use wit_get_work_items_for_iteration for the active iteration. Read title, state, story points, and tags. Also use work_get_team_settings to confirm Sprint dates.
• Jira: use the active sprint reporting tools to read issue states and progress.
• Manual: ask "Give me a quick brief — what has been completed, what is in progress, what is at risk, and how many days remain in the Sprint?"

Calculate:

• Sprint progress: days elapsed vs. total Sprint days
• Story point progress: points Done vs. total committed
• Items at risk: any work item In Progress with less than 2 days to Sprint end and not nearly complete

---

Step 3 — Assess Sprint health

Before writing, form a clear picture of the Sprint's trajectory: