Skill

Skill: expectations-reset

Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-stakeholder-delivery

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-distillator

7 files

Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: expectations-reset

Purpose

Facilitate a structured reset of stakeholder expectations after a scope change, timeline slip, or delivery failure — without destroying trust.

When to Use

Release date has moved by more than 2 weeks
Significant scope has been cut
A committed feature will not be delivered as promised

Framework: Expectations Reset

Step 1 — Acknowledge Before Explaining

Never lead with reasons. Lead with acknowledgment.

"I want to be transparent with you about a change to our delivery plan."

Step 2 — State What Changed

Be precise:

What was committed → what is now the reality
Use specific numbers and dates, not vague language

Step 3 — Explain Root Cause (Brief)

One or two sentences. No blame, no excuses.

"This was caused by [X]. We identified it on [date]."

Step 4 — New Commitment

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."

Step 5 — What We're Doing Differently

Show that the same problem won't happen again:

Process change
Risk mitigation
Monitoring improvement

Step 6 — Invite Questions

Close by inviting dialogue, not just passive acceptance.

Output Format

Conversation script (verbal or written)
FAQ: anticipated questions with prepared answers
Suggested next command: /status-update or /steering-deck