Skill

Skill: delay-communication

Craft professional, clear, and constructive communication when a delivery is delayed. Protects stakeholder trust while presenting a credible recovery plan.

Install

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Craft professional, clear, and constructive communication when a delivery is delayed. Protects stakeholder trust while presenting a credible recovery plan.

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-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

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: delay-communication

Purpose

Craft professional, clear, and constructive communication when a delivery is delayed. Protects stakeholder trust while presenting a credible recovery plan.

When to Use

Release date needs to move
Sprint scope will not be delivered as planned
External dependency causes timeline slip
Scope changes force a delay

Framework: Delay Communication

Principle: The 4 C's

Every delay communication must cover:

Clarity — What exactly is delayed, by how much
Cause — Why it happened (factual, no blame)
Consequence — What the impact is on downstream plans
Correction — What the recovery plan is

Step 1 — Gather Information

Ask for:

What was the original commitment (date, scope)?
What is the new expected date or reduced scope?
Root cause of the delay
What has been done to recover?
Who is the audience (team, stakeholders, executives)?

Step 2 — Draft the Communication

Subject: Delivery Update: [Feature/Release Name] — Timeline Adjustment

Opening (1 sentence): State the situation directly and without softening language.

"The [Release Name] delivery has been revised from [original date] to [new date]."

Context (2–3 sentences): Explain the cause factually.

"The delay was caused by [root cause]. This was identified on [date] when [event/signal]."

Impact (1–2 sentences): State downstream consequences clearly.

"This affects [dependent teams/features/commitments]. [Downstream item] will now [move/adjust by X]."

Recovery Plan (bullet list):

What actions are being taken
By whom
By when
What will be delivered by the revised date

What We Need (if anything): State explicit asks: decisions, approvals, resource support.

Closing: One line expressing ownership and commitment.

Step 3 — Tone Calibration

Adjust based on audience:

Team: Direct, action-focused, collaborative
Stakeholders: Professional, factual, solution-oriented
Executive: Brief, impact-first, decision-ready

Output Format

Ready-to-send communication (email or message format)
Talking points for verbal delivery
Suggested next command: /status-update or /steering-deck