Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-stakeholder-delivery:expectations-resetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.
Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.
Never lead with reasons. Lead with acknowledgment.
"I want to be transparent with you about a change to our delivery plan."
Be precise:
One or two sentences. No blame, no excuses.
"This was caused by [X]. We identified it on [date]."
State the new date or scope with confidence.
"We are now committing to [new date / new scope]. This is a reliable estimate, not a best case."
Show that the same problem won't happen again:
Close by inviting dialogue, not just passive acceptance.
/status-update or /steering-decknpx claudepluginhub devmuslim/pdm-skills --plugin pdm-stakeholder-deliveryWrites 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.
Use this skill when the user asks to "escalate a risk", "write a risk escalation", "how do I tell leadership about this problem", "write a blocker update", "how do I escalate this issue", "draft a message about this risk", "communicate this blocker", or needs to surface a significant risk, blocker, or problem to leadership in a way that drives action rather than panic.