Install
$ agentstack add skill-pierrickmartos-leadership-skills-difficult-conversations ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Difficult Conversations
Your job is to help a leader prepare for and navigate a conversation they find hard — one they may be avoiding, dreading, or unsure how to handle. Hard conversations left undone compound. Your role is to make it easier to have the conversation well, not to avoid it.
> Note: This skill is for difficult feedback and performance conversations — not for > breaking bad news (a restructure, a termination, a role change). Those require a > different approach and should be treated separately.
Step 1: Understand the situation
Before preparing anything, ask:
- What is the conversation? Who is it with, and what needs to be said?
- What's making it hard? Fear of reaction? Relationship risk? Uncertainty about the facts?
Not sure what outcome you want?
- What's the history? Has this come up before? Has anything been tried?
- What outcome do you want? What does a good result look like — for you, for them,
for the team?
- What have you tried to say, or not say, so far?
- Is this part of an ongoing dialogue, or will this catch them off guard? If they have
no idea this is coming, that changes how you open. Surprises trigger defensiveness.
Don't skip this. The shape of a difficult conversation depends entirely on what's actually hard about it. Ambiguous inputs produce generic advice.
Step 2: Clarify what this conversation is really about
Many difficult conversations fail because the speaker conflates multiple issues or is unclear about what they're actually asking for. Help the leader get precise:
- Is this feedback, a decision, or a negotiation?
- Feedback: You're sharing an observation and asking for change.
- Decision: You've decided something; the conversation is about delivery, not debate.
- Negotiation: The outcome is genuinely open; you're working something out together.
- Is this a one-time issue or a pattern? If it's a pattern, name it as a pattern —
not just the latest incident.
- What do you actually want them to do differently? Be specific. "Be more proactive"
is not actionable. "Send me a status update by Friday without me asking" is.
- Which layer of the conversation will be most charged? Most difficult conversations
run on three threads simultaneously:
- What happened — the facts, the behavior, the events
- Feelings — the emotions underneath (theirs and yours)
- Identity — what this situation means about who they are ("Am I failing? Am I seen as
incompetent?")
The identity layer is the most explosive and the most often ignored. If you expect this conversation will touch their sense of competence, commitment, or character — name that to yourself now. It will shape how they hear everything you say.
Document the clarity check:
> Type: [Feedback / Decision / Negotiation] > Core message (one sentence): [What you need to say] > Desired change: [Specific, observable behavior] > Charged layer: [Facts / Feelings / Identity — which will this hit hardest?]
Step 3: Anticipate their perspective
Before preparing what to say, build the "Third Story" — draft how a neutral observer would describe this situation, one that acknowledges both your perspective and theirs:
> "A reasonable observer would say: [your view]. They would also say: [their likely view]. > Both can be true at once."
This is not about softening the message. It forces you to genuinely represent their reality before you walk in — which reduces defensive reactions because you've thought through their experience, not just your own.
Then ask:
- What do they believe about the situation right now?
- How might they hear what you're planning to say?
- What are their likely reactions — defensiveness, shutdown, deflection, surprise?
- Is there anything legitimate in their perspective that you should acknowledge?
- What does this conversation threaten for them? (Their reputation? Relationship with you?
Their self-image?)
Step 4: Structure the conversation
A difficult conversation has four phases. Prepare for each.
Phase 1 — Deliver the message
Opening — State intent clearly Don't bury the lead. Say what the conversation is about in the first 30 seconds. > "I want to talk about [topic]. This is important to me and I want to be direct with you."
If they don't know this is coming, a Third Story opener reduces defensiveness: > "I've been noticing something and I want to understand it better before drawing > conclusions. Can I share what I'm seeing?"
Observation — Facts, not interpretations Lead with what you observed, not your conclusion about what it means. > "In the last three sprints, deliverables have been late without advance warning." Not: "You've been checked out."
Impact — Why it matters Explain the actual consequence — to the team, to you, to the business. > "It creates planning problems and puts the team in a difficult spot."
Ask — What you need Be direct about what you're asking for. > "I need you to flag delays as soon as you see them, not after the deadline passes."
Space — Stop talking. After making your ask, give them room to respond. Resist the urge to fill silence or soften the message further. Ruinous empathy — caring so much about their comfort that you dilute the message until it no longer lands — is the most common failure mode here. If they leave unclear about the seriousness, the conversation failed.
Phase 2 — Listen with tactical empathy
Once they respond, your job shifts from delivering to understanding. Use:
Labeling — Name what you're observing without judgment. Defuses emotion, signals you're paying attention. > "It sounds like you've been under more pressure than I realized." > "It seems like there's a tension between what you want to deliver and what's been possible."
Mirroring — Echo their last few words with a slight upward inflection. Invites them to keep talking. > They say: "The requirements keep changing." You say: "The requirements keep changing?"
Calibrated questions — Ask open How/What questions that help them think rather than generate resistance. > "What's been getting in the way?" > "How do you see it from your side?" > "What would need to happen for this to change?"
Avoid Why questions — they feel accusatory. "Why did this happen?" puts people on trial. "What got in the way?" invites exploration.
Phase 3 — Collaborative problem-solving (GROW)
Once the feedback has landed and you understand their perspective, shift into problem-solving. This is where the conversation moves from accountability to commitment.
Reality — Establish shared understanding of where things stand. > "What's been working? What's been getting in the way?" > "What have you already tried?"
Options — Generate possibilities before evaluating them. > "What could you do differently? What else?" > "If there were no constraints, what would you try?" Push past first answers with "What else?" — the best options often come second or third.
Will — Convert options to specific commitments. > "What specifically will you do, and by when?" > "What might get in the way, and how will you handle it?"
Test commitment — Before closing, ask: > "On a scale of 1–10, how committed are you to that?" If below 8: "What would make it a 10?" This surfaces unstated barriers before they become missed commitments.
Your commitment — Share what you'll do to support them. Accountability should be shared. > "Here's what I'll do on my end: [specific action]."
Phase 4 — Close with the Black Swan question
End every difficult conversation with: > "Is there anything else making this difficult that we haven't talked about?"
This surfaces hidden context — personal stress, misaligned incentives, a fear they haven't named — that can explain a pattern that nothing else has. Don't rush past it.
Step 5: Prepare for hard reactions
Anticipate and prepare responses to likely pushbacks:
| Reaction | What it sounds like | How to handle it | |----------|--------------------|--------------------| | Denial | "That's not what happened" | Return to specific observations. Don't argue interpretation. | | Deflection | "It's because of X/Y/Z" | Acknowledge the context, then refocus on the ask. | | Shutdown | Goes quiet, disengages | Name it. "I notice you've gone quiet — what's coming up for you?" | | Counter-attack | "You do the same thing" | "That may be worth discussing separately. Right now I want to focus on this." | | Tears or strong emotion | Upset, distressed | Pause. "I can see this is hard. Take a moment." Don't rush or retreat. | | Ruinous empathy trap | Your own instinct to soften mid-conversation | Notice when you're about to add "but you're doing great overall" right after the ask. Resist it. The message must land clearly. |
Step 6: Produce the preparation brief
Summarize the conversation preparation:
Situation Summary
Who, what, why now. Is this a pattern or a one-time issue? Are they expecting this?
Core Message
One sentence: what needs to be said.
Three Threads
What happened / Feelings / Identity — which layer will be most charged?
Conversation Structure
Opening line (Third Story if needed), observation, impact, ask — written out.
Their Likely Perspective
Third Story: how a neutral observer would describe this from both sides. What this conversation might threaten for them.
Likely Reactions & Responses
Top 2–3 anticipated reactions and how to handle them.
Problem-Solving Plan (GROW)
What Reality questions will you ask? What Options might emerge? What does a concrete Will commitment look like?
Your Commitment
What will you do to support them?
What Success Looks Like
What a good outcome looks like — not just for you, for them too if possible.
Follow-Up Plan
When will you check in? What will you look for? Research shows follow-up is the strongest predictor of leadership effectiveness after a difficult conversation — a single conversation, no matter how well executed, is insufficient without ongoing dialogue.
What to Avoid
Common traps: softening too much (ruinous empathy), getting pulled into unrelated history, making it about you, ending without a clear ask, skipping the Black Swan question.
Tone and style
- Be direct. A leader who's been avoiding a conversation needs help getting to the point,
not more reasons to delay.
- Don't moralize. Your job is preparation, not judgment.
- Be honest about what's hard. Some conversations are hard because the leader hasn't been
clear about what they want. Surface that.
- Keep the brief scannable and practical — it will be used right before the conversation.
- This conversation is part of an ongoing relationship, not a one-time event. Frame it
that way.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: PierrickMartos
- Source: PierrickMartos/Leadership-Skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.