difficult-workplace-conversations
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
Best use case
difficult-workplace-conversations is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "difficult-workplace-conversations" skill to help with this workflow task. Context: Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/difficult-workplace-conversations/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How difficult-workplace-conversations Compares
| Feature / Agent | difficult-workplace-conversations | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Difficult Conversations Skill A structured framework for approaching challenging workplace conversations including conflicts, performance issues, sensitive feedback, and emotionally charged discussions. ## When to Use This Skill - Preparing for a challenging conversation with a colleague - Addressing performance issues with a team member - Delivering difficult feedback to a peer or manager - Navigating conflict between team members - Discussing sensitive topics (salary, promotion, termination) - Handling emotional or defensive reactions - Following up after difficult discussions ## Core Framework: Preparation-Delivery-Followup Difficult conversations succeed or fail based on three phases: ### Phase 1: Preparation (Before) **Purpose:** Set yourself up for a productive conversation 1. **Clarify the Issue** - What specifically happened? (Observable facts only) - What is the impact? (On you, team, work) - What do you need to change? 2. **Check Your Emotions** - What am I feeling? Why? - Am I calm enough to have this conversation? - What might trigger me during this conversation? 3. **Consider Their Perspective** - How might they see this situation? - What constraints or pressures might they have? - What do they care about that I can acknowledge? 4. **Define Your Goal** - What outcome do I want? - What is the minimum acceptable result? - What am I willing to compromise on? ### Phase 2: Delivery (During) **Purpose:** Have the conversation effectively 1. **Open Neutrally** - Start with facts, not judgments - Express intent to understand, not accuse - Create psychological safety 2. **Share Your Perspective** - Describe behavior, not character - Focus on impact, not intention - Use "I" statements, not "you always" 3. **Listen Actively** - Ask clarifying questions - Acknowledge their viewpoint - Look for shared interests 4. **Seek Resolution** - Propose specific actions - Agree on next steps - Set check-in timeline ### Phase 3: Followup (After) **Purpose:** Ensure lasting resolution 1. **Document Agreements** - What was agreed? - Who does what by when? - How will you measure success? 2. **Check Progress** - Follow up as promised - Acknowledge improvements - Address continued issues promptly 3. **Maintain Relationship** - Separate issue from person - Rebuild trust over time - Watch for regression ## Key Principles ### Separate Impact from Intent **What happened:** Observable behavior **What I felt:** Your emotional response **What I assume:** Their intention (often wrong) Focus conversation on behavior and impact, not assumed intentions. ### The SBI Model **Situation:** When and where did this happen? **Behavior:** What specifically did they do/say? **Impact:** What was the effect on you, the team, or the work? ### Managing Emotions | If You Feel | Before Acting | | ----------- | ------------- | | Angry | Wait 24 hours, write but don't send | | Hurt | Talk to neutral party first | | Anxious | Practice the conversation | | Defensive | Identify your contribution | ### When to Escalate Escalate when: - Safety is at risk - Legal issues involved - Repeated conversations haven't worked - Power dynamics prevent resolution - You need documentation ## Conversation Types ### Performance Feedback - Lead with specific examples - Connect to expectations/standards - Focus on future improvement - Offer support and resources ### Conflict Resolution - Hear both sides separately first - Identify underlying interests - Look for win-win solutions - Document agreements ### Sensitive Topics - Choose private, neutral setting - Allow time for processing - Be direct but compassionate - Respect confidentiality ### Receiving Feedback - Thank them for feedback - Ask clarifying questions - Don't defend immediately - Reflect before responding ## References (Load When Needed) ### Detailed Frameworks - **[Conversation Framework](references/conversation-framework.md)**: Complete three-phase framework with scripts and examples - **[Preparation Template](references/preparation-template.md)**: Worksheet for preparing before difficult conversations - **[Delivery Scripts](references/delivery-scripts.md)**: Opening lines, response handling, reframing techniques - **[Emotional Regulation](references/emotional-regulation.md)**: Managing your own emotions before and during ## See Also - `feedback-mastery` skill - SBI feedback model (overlaps but more feedback-focused) - `professional-effective-communication` skill - General communication patterns ## Example Scenarios ### Scenario 1: Addressing Missed Deadlines ```markdown **Issue:** Team member missed 3 deadlines in past month **Impact:** Project delayed, others blocked **Goal:** Understand root cause, agree on prevention plan **Opening:** "I wanted to check in about the recent deliverables. I've noticed the last three have come in past deadline, and I'd like to understand what's happening and how we can address it together." ``` ### Scenario 2: Peer Conflict ```markdown **Issue:** Colleague publicly criticized your work in meeting **Impact:** Embarrassed, trust damaged **Goal:** Address behavior, rebuild working relationship **Opening:** "I'd like to talk about what happened in yesterday's standup. When you said my code 'missed obvious issues,' I felt called out in front of the team. I'd like to understand your concerns and find a better way to handle code quality feedback." ``` ### Scenario 3: Asking Manager for Raise ```markdown **Issue:** Feel underpaid relative to market/contribution **Impact:** Demotivation, considering leaving **Goal:** Discuss compensation, get timeline or adjustment **Opening:** "I'd like to discuss my compensation. I've been here two years, taken on the payments project leadership, and want to make sure my salary reflects my contributions and the current market." ``` ## Anti-Patterns to Avoid ### In Preparation - **Scripting every word** - You'll sound robotic; prepare themes, not scripts - **Building a case** - This isn't a trial; seek understanding, not winning - **Waiting too long** - Issues compound; address promptly ### In Delivery - **Starting with "You always..."** - Triggers defensiveness immediately - **Burying the lead** - Get to the point; don't soften excessively - **Asking leading questions** - "Don't you think..." isn't asking ### In Followup - **Forgetting to check in** - Without follow-up, nothing changes - **Holding grudges** - Issue resolved means relationship continues - **Over-documenting** - Not everything needs written record ## Success Metrics A successful difficult conversation: - Both parties feel heard - Specific actions are agreed - Relationship is preserved or improved - The issue doesn't recur (or has clear escalation) - Neither party is blindsided later
Related Skills
remembering-conversations
Use when user asks 'how should I...' or 'what's the best approach...' after exploring code, OR when you've tried to solve something and are stuck, OR for unfamiliar workflows, OR when user references past work. Searches conversation history.
azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
raindrop-io
Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.
zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式,自动转换,一键创建知识库。
discover-skills
当你发现当前可用的技能都不够合适(或用户明确要求你寻找技能)时使用。本技能会基于任务目标和约束,给出一份精简的候选技能清单,帮助你选出最适配当前任务的技能。
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
project-to-obsidian
将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则(默认到 00_Inbox/AI/、追加式、统一 Schema) 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】: - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建(先到 00_Inbox/AI/) - 禁止自作主张决定输出位置
obsidian-helper
Obsidian 智能笔记助手。当用户提到 obsidian、日记、笔记、知识库、capture、review 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入三条硬规矩(00_Inbox/AI/、追加式、白名单字段) 3. 按 STEP 0 → STEP 1 → ... 顺序执行 4. 不要跳过任何步骤,不要自作主张 【禁止行为】: - 禁止不读 SKILL.md 就开始工作 - 禁止跳过用户确认步骤 - 禁止在非 00_Inbox/AI/ 位置创建新笔记(除非用户明确指定)
internationalizing-websites
Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.
google-official-seo-guide
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
github-release-assistant
Generate bilingual GitHub release documentation (README.md + README.zh.md) from repo metadata and user input, and guide release prep with git add/commit/push. Use when the user asks to write or polish README files, create bilingual docs, prepare a GitHub release, or mentions release assistant/README generation.
doc-sync-tool
自动同步项目中的 Agents.md、claude.md 和 gemini.md 文件,保持内容一致性。支持自动监听和手动触发。