difficult-workplace-conversations
Skill0 starsChanged 4 months agoMITView on GitHub
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.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Ivan-propio/claude-skillsword for word, first seen Nov 16, 2026
- Samueladewole/claude-skillsword for word, first seen Oct 13, 2026
- digitalspeed/claude-code-skillsetword for word, first seen Jun 17, 2026
Other versions3 projects use a version of this.
Word for word · 3
- digitalspeed/claude-code-skillset★ 1100% same
- Ivan-propio/claude-skills★ 0100% same
- Samueladewole/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- agent-md-refactorSkill
- backend-to-frontend-handoff-docsSkill
- c4-architectureSkill
- codexSkill
- command-creatorSkill
- commit-workSkill
- crafting-effective-readmesSkill
- daily-meeting-updateSkill
- database-schema-designerSkill
- datadog-cliSkill
- dependency-updaterSkill
- agency-brand-guardianSkill
- design-system-starterSkill
- agency-ui-designerSkill
- agency-ux-researcherSkill
- domain-name-brainstormerSkill
- draw-ioSkill
- agency-ai-data-remediation-engineerSkill
- agency-ai-engineerSkill
- agency-api-platform-engineerSkill
- agency-autonomous-optimization-architectSkill
- agency-backend-architectSkill
- agency-cms-developerSkill
- agency-codebase-onboarding-engineerSkill
- agency-code-reviewerSkill
- agency-database-optimizerSkill
- agency-database-reliability-engineerSkill
- agency-data-engineerSkill
- agency-data-visualization-engineerSkill
- agency-desktop-app-engineerSkill
- agency-devops-automatorSkill
- agency-drupal-performance-engineerSkill
- agency-drupal-shopping-cart-engineerSkill
- agency-email-intelligence-engineerSkill
- agency-embedded-firmware-engineerSkill
- agency-feishu-integration-developerSkill
- agency-filament-optimization-specialistSkill
- agency-finops-engineerSkill
- agency-frontend-developerSkill
- agency-gaussdb-expert-engineerSkill
- agency-git-workflow-masterSkill
- agency-internationalization-engineerSkill
- agency-identity-access-engineerSkill
- agency-incident-response-commanderSkill
- agency-iot-fleet-engineerSkill
- agency-it-service-managerSkill
- agency-llm-post-training-engineerSkill
- agency-minimal-change-engineerSkill
- agency-mobile-app-builderSkill
- agency-mobile-release-engineerSkill
- agency-multi-agent-systems-architectSkill
- agency-network-engineerSkill
- agency-orgscript-engineerSkill
- agency-payments-billing-engineerSkill
- agency-privacy-engineerSkill
- agency-prompt-engineerSkill
- agency-rag-pipeline-engineerSkill
- agency-rapid-prototyperSkill
- agency-realtime-collaboration-engineerSkill
- agency-rust-refactoring-specialistSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Start with facts, not judgments
- Distinctive: line 61
Use "I" statements, not "you always"
- Distinctive: line 66
Look for shared interests
- Distinctive: line 75
Purpose: Ensure lasting resolution
- Distinctive: line 83
Follow up as promised
- Distinctive: line 104
Situation: When and where did this happen?
- Distinctive: line 140
Look for win-win solutions
- Distinctive: line 154
Don't defend immediately
- Distinctive: line 228
Over-documenting: - Not everything needs written record
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Clarify the Issue
- What specifically happened? (Observable facts only)
- What is the impact? (On you, team, work)
- What do you need to change?
- Check Your Emotions
- What am I feeling? Why?
- Am I calm enough to have this conversation?
- What might trigger me during this conversation?
- 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?
- 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
- Open Neutrally
- Start with facts, not judgments
- Express intent to understand, not accuse
- Create psychological safety
- Share Your Perspective
- Describe behavior, not character
- Focus on impact, not intention
- Use "I" statements, not "you always"
- Listen Actively
- Ask clarifying questions
- Acknowledge their viewpoint
- Look for shared interests
- Seek Resolution
- Propose specific actions
- Agree on next steps
- Set check-in timeline
Phase 3: Followup (After)
Purpose: Ensure lasting resolution
- Document Agreements
- What was agreed?
- Who does what by when?
- How will you measure success?
- Check Progress
- Follow up as promised
- Acknowledge improvements
- Address continued issues promptly
- 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: Complete three-phase framework with scripts and examples
- Preparation Template: Worksheet for preparing before difficult conversations
- Delivery Scripts: Opening lines, response handling, reframing techniques
- Emotional Regulation: Managing your own emotions before and during
See Also
feedback-masteryskill - SBI feedback model (overlaps but more feedback-focused)professional-effective-communicationskill - General communication patterns
Example Scenarios
Scenario 1: Addressing Missed Deadlines
**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
**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
**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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

