plugins/pm-comms/skills/difficult-conversation/SKILL.md
Prepare for and script a hard conversation — conflict, bad news, a boundary, an apology. Use when asked to prepare for a difficult conversation, address a conflict, deliver bad news, confront a colleague, or have a hard talk with a manager/report/peer. Produces a prep brief — the real goal, the other side's likely view, an opening line, the key points, anticipated reactions with responses, and the outcome you want.
npx skillsauth add mohitagw15856/pm-claude-skills difficult-conversationInstall 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.
The conversations we avoid are usually the ones that matter most — and we botch them by winging it or over-rehearsing into a script that shatters on first contact. This skill preps the hard talk the way the research says works: get clear on the actual goal, understand the other person's story, open without triggering defensiveness, and plan for their reactions — so you go in calm and come out with the relationship intact.
Ask for these only if they aren't already provided:
1. Your real goal — name it plainly (and the un-goal — e.g. "not to win, but to change X"). Conversations go wrong when the unspoken goal is to be proven right.
2. Their story — how they likely see it and what they need to feel (heard, respected, safe). You can't move someone you haven't understood.
3. Open — a specific opening line that states the issue from the facts + your impact, not blame ("When the deadline slipped, I was left explaining it to the client" — not "You always miss deadlines"). The first 30 seconds set the tone.
4. Key points — the 2–3 things you must convey, each separating observation from story/judgement.
5. Likely reactions → your response — defensiveness, deflection, emotion, counterattack — and a calm, non-escalating reply prepared for each.
| If they… | You respond… | |---|---|
6. Land it — the ask or agreement you want, and how to close on a concrete next step.
Stance note — stay curious, not certain; aim for a shared understanding, not a verdict.
Crucial Conversations (Patterson et al.) and Difficult Conversations (Stone, Patton, Heen) — facts vs. story, the third story, safety.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.