Skip to main content
ClaudeWave
Skill2k repo starsupdated 3mo ago

difficult-workplace-conversations

This Claude Code skill provides a structured preparation-delivery-followup framework for managing difficult workplace conversations involving conflicts, performance issues, sensitive feedback, and emotionally charged discussions. Use it when preparing for challenging conversations with colleagues or managers, addressing performance problems, delivering critical feedback, navigating team conflicts, discussing sensitive topics like salary or promotion, or following up after difficult discussions to ensure lasting resolution and relationship repair.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/softaworks/agent-toolkit /tmp/difficult-workplace-conversations && cp -r /tmp/difficult-workplace-conversations/skills/difficult-workplace-conversations ~/.claude/skills/difficult-workplace-conversations
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# 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 Prepa
commandsSkill

Add a skill to the project with validation and README generation

sync-skills-readmeSlash Command

Sync root README.md with current skills inventory from skills/ directory

ascii-ui-mockup-generatorSubagent

Use this agent when you need to visualize UI concepts through ASCII mockups before implementation. Examples: <example>Context: User has an idea for a dashboard layout with data tables and charts. user: 'I want to create a dashboard that shows user analytics with a sidebar navigation, main content area with charts, and a data table below' assistant: 'I'll use the ascii-ui-mockup-generator agent to create multiple ASCII mockup variations for your dashboard concept.' <commentary>The user wants to visualize a UI concept, so use the ascii-ui-mockup-generator to create multiple ASCII representations they can choose from.</commentary></example> <example>Context: User is designing a form layout with multiple input fields. user: 'I need a contact form with name, email, message fields and a submit button' assistant: 'Let me use the ascii-ui-mockup-generator to create several ASCII mockup options for your contact form layout.' <commentary>Since the user needs to visualize form layouts, use the ascii-ui-mockup-generator to provide multiple ASCII design options.</commentary></example>

codebase-pattern-finderSubagent

codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!

communication-excellence-coachSubagent

PROACTIVELY use when reviewing communication drafts or preparing difficult conversations. Provides email refinement, tone calibration, roleplay practice, and presentation feedback with actionable suggestions.

general-purposeSubagent

Default agent for handling complex, multi-step tasks with automatic delegation capabilities

mermaid-diagram-specialistSubagent

Mermaid diagram specialist for creating flowcharts, sequence diagrams, ERDs,

ui-ux-designerSubagent

Expert UI/UX design critic and advisor who provides research-backed, opinionated feedback on interfaces. Use when you need honest assessment of design decisions, want to avoid generic "AI slop" aesthetics, need evidence-based UX guidance, or want distinctive design direction grounded in actual user behavior research. This agent will push back on bad ideas and cite sources for every recommendation.