skills/having-difficult-conversations/SKILL.md
Help users navigate tough feedback, performance conversations, and conflict. Use when someone needs to give hard feedback, have a performance conversation, fire someone, address conflict with a colleague, or deliver disappointing news like a denied promotion.
npx skillsauth add cvillamarp-lgtm/skillspodcast having-difficult-conversationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user navigate tough conversations with courage and skill using frameworks from 43 product leaders.
When the user asks for help with a difficult conversation:
| Situation | Framework | Template | |---|---|---| | Performance feedback | SBI | "In [situation], when you [behavior], the impact was [impact]." | | Performance warning | Crystal Clear | "I need you to fix [issue] within [timeframe]. Otherwise, we're going to have to part ways." | | Firing | Brief confirmation + HR | "We talked about this. You haven't made the changes. We're going to part ways. [HR] will walk through logistics." | | Peer conflict | NVC | "When [observation], I feel [feeling], because I need [need]. Would you be willing to [request]?" | | Bad news (denied promo, etc.) | Hope + path forward | "I know this is hard to hear. [Decision + reason]. I'm committed to your success — here's what I'd like to do next." | | Defensive reaction | Perception check | "What did you hear me say?" |
SBI (Situation-Behavior-Impact):
In ______ (meeting/situation), when you ______ (observable behavior), it ______ (impact on you/team).
NVC (Nonviolent Communication):
When ______ (objective observation), I feel ______ (emotion word, not "I feel that..."), because I need ______ (underlying need). Would you be willing to ______ (specific request)?
CORE (Context-Observation-Result-nExt step):
Context: In ______ / Observation: when you ______ / Result: it ______ / Next step: I'd like you to ______.
Crystal Clear Warning:
I need you to ______ within the next ______ days. Otherwise, we're going to have to part ways. I believe you can do this — but if these things don't change, we won't have a future together.
Termination:
We've talked about this multiple times. The last time, I told you what needed to change. Those changes haven't happened, and we're going to part ways. [HR person] is here to walk through logistics.
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.