delay-communication

Generate delay communications using the 4 C's framework for varied audiences.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/devmuslim/pdm-skills --skill delay-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delay-communication
Source: https://github.com/devmuslim/pdm-skills/tree/main/pdm-stakeholder-delivery/skills/delay-communication
Command: npx skills add https://github.com/devmuslim/pdm-skills --skill delay-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you craft clear, professional, and constructive communications when a delivery is delayed, preserving stakeholder trust and outlining a credible recovery plan.

Core Features & Use Cases

  • Structured Communication: Provides a framework (The 4 C's: Clarity, Cause, Consequence, Correction) for delay announcements.
  • Audience Adaptation: Offers guidance on adjusting tone for different audiences (Team, Stakeholders, Executive).
  • Use Case: A critical external dependency has caused a release date to slip. Use this skill to draft an email to stakeholders explaining the delay, its cause, impact, and the recovery plan.

Quick Start

Use the delay-communication skill to draft an email announcing a delay for the 'Q4 Feature Release'.

Frequently Asked Questions about delay-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I communicate a project delay to stakeholders professionally?

To communicate a project delay professionally, use the 4 C's framework: Clarity, Cause, Consequence, and Correction. This structure ensures stakeholder messages explain the delay, its impact, and the recovery plan while preserving trust.

What should be included in a delivery delay announcement email?

A delivery delay announcement email should include the 4 C's: Clarity of the delay, its Cause, the Consequence or impact on the release schedule, and the Correction plan. It must be tailored to the audience to maintain effective stakeholder management.

How do I adjust my communication tone for executives versus team members during a release delay?

Adjust communication tone for executives versus team members by adapting the 4 C's framework for each audience. The delay-communication process tailors the message depth, focusing on strategic risk mitigation for executives while providing direct project status updates for teams.

What is the best way to explain a release date slip caused by an external dependency?

The best way to explain a release date slip caused by an external dependency is to apply the 4 C's structure. State the delay clearly, identify the external dependency as the cause, outline the consequence, and provide a credible correction plan.

Can I get talking points for verbally announcing a delayed release to stakeholders?

Yes, you can generate talking points for verbally announcing a delayed release. The process provides output in both email/message formats and verbal talking points, ensuring clear stakeholder communication and risk mitigation across different delivery mediums.

When do I need a structured framework for project delay communication?

You need a structured framework for project delay communication when a delivery is delayed and stakeholder trust is at risk. Using the 4 C's ensures your project status update clearly conveys the problem, impact, and recovery plan to teams and executives.