Bad news delivery skills
Deliver difficult news with clarity and respect using the DIRECT framework. Covers missed deadlines, rejections, cancellations, and price increases with templates and timing guidance.From its SKILL.md
npx -y skills add mcltyl/bad-news-delivery-skillsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.9 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
Bad News Delivery
Deliver difficult news with clarity and respect. Stop delaying, start communicating.
When to Use
- Missed deadline or deliverable
- Project cancellation or scope cut
- Rejection (job offer, proposal, request)
- Performance issues or negative feedback
- Service disruption or failure
- Price increase or policy change
The Problem
People delay bad news because they fear the reaction. But delay makes everything worse:
- The recipient loses time to adjust
- Trust erodes when they find out you knew
- Your anxiety compounds daily
Truth: Bad news doesn't improve with age. Clarity is kindness.
The Framework
DIRECT Method
| Step | Action | Purpose |
|---|---|---|
| D | Declare | State the news in the first sentence |
| I | Inform | Give essential context (what happened, why) |
| R | Responsibility | Own your part, if any |
| E | Exit path | Offer next steps or alternatives |
| C | Check | Open for questions |
| T | Timeline | Set expectations for follow-up |
Anti-Patterns to Avoid
| Pattern | Example | Problem |
|---|---|---|
| Buried lede | "So I wanted to touch base about the project timeline, and there are some considerations..." | Reader anxious for 3 paragraphs |
| Over-apologizing | "I'm so so sorry, I feel terrible, I know this is awful..." | Makes it about YOUR feelings |
| Blame-shifting | "Due to circumstances beyond our control..." | Erodes trust |
| False hope | "It's not great, but maybe..." | Delays acceptance |
| Ghosting | [no response] | Worst option |
Templates
Professional: Missed Deadline
Subject: [Project] Delivery Update - New Timeline
[Name],
The [project/deliverable] will not be ready by [original date]. The new delivery date is [new date].
What happened: [Brief, honest explanation - 1-2 sentences]
What I'm doing: [Concrete actions to deliver]
Impact mitigation: [How you're reducing the damage]
I'm available to discuss this [time] if helpful. Let me know what questions you have.
[Name]
Professional: Rejecting a Candidate
Subject: Update on your application - [Role]
Hi [Name],
Thank you for interviewing for the [Role] position. After careful consideration, we've decided to move forward with another candidate.
This was a competitive process, and your [specific strength] stood out. Ultimately, we chose someone whose experience in [specific area] more closely matched our immediate needs.
[Optional: I'd encourage you to apply for future roles / I'm happy to connect you with [other opportunity]]
I appreciate the time you invested in our process.
Best,
[Name]
Personal: Canceling Plans
Hey [Name],
I need to cancel our [plans] on [date]. [One sentence reason - keep it simple]
I'm sorry for the late notice. Can we reschedule for [suggest specific alternative]?
[Name]
Business: Price Increase
Subject: Important update to your [service] pricing
Hi [Name],
Starting [date], your [service] rate will change from [old price] to [new price].
Why: [Honest reason - costs, value addition, market adjustment]
What stays the same: [Reassure about continuity]
What's new: [If applicable, any added value]
If you have questions or want to discuss your account, reply to this email or book time here: [link]
Thank you for being a customer.
[Name]
Delivery Timing Guide
| Situation | Best Time | Worst Time |
|---|---|---|
| Work deadline miss | As soon as you know | Day of deadline |
| Rejection after interview | Within 48 hours | After 2+ weeks |
| Personal plan cancel | 24+ hours before | Day of |
| Price/policy change | 30+ days notice | Effective immediately |
| Performance feedback | Private, scheduled | Public, surprise |
The 10-Second Rule
If you've been sitting on bad news for more than 10 seconds of deliberation, you're already late. The discomfort you feel is a signal to act, not wait.
Checklist Before Sending
- News is in the first sentence
- No unnecessary preamble
- Context is brief and honest
- I've owned my part (if applicable)
- Clear next step or alternative offered
- Tone is respectful, not groveling
- I've read it as the recipient would
Response Handling
After delivering bad news, expect one of these responses:
| Response | Your Move |
|---|---|
| Anger | Acknowledge, don't defend. "I understand this is frustrating." |
| Questions | Answer directly, don't over-explain |
| Silence | Give space, follow up once if needed |
| Negotiation | Be clear on what's flexible and what isn't |
| Acceptance | Express appreciation, move to next steps |
Respect people enough to tell them the truth.
What ships with it: 1 file
1.9 KB alongside SKILL.md
- README.md1.9 KB