Craft professional, clear, and constructive communication when a delivery is delayed. Protects stakeholder trust while presenting a credible recovery plan.
npx claudepluginhub devmuslim/pdm-skills --plugin pdm-stakeholder-deliveryThis skill uses the workspace's default tool permissions.
Craft professional, clear, and constructive communication when a delivery is delayed. Protects stakeholder trust while presenting a credible recovery plan.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
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.
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.
Craft professional, clear, and constructive communication when a delivery is delayed. Protects stakeholder trust while presenting a credible recovery plan.
Every delay communication must cover:
Ask for:
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 We Need (if anything): State explicit asks: decisions, approvals, resource support.
Closing: One line expressing ownership and commitment.
Adjust based on audience:
/status-update or /steering-deck