跳到正文
cccskills
免费在 GitHub 公开

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.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(6)

  • SKILL.md7.1 KB
  • README.md9.0 KB
  • references/conversation-framework.md9.2 KB
  • references/delivery-scripts.md8.6 KB
  • references/emotional-regulation.md8.6 KB
  • references/preparation-template.md7.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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 FeelBefore Acting
AngryWait 24 hours, write but don't send
HurtTalk to neutral party first
AnxiousPractice the conversation
DefensiveIdentify 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

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

**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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

中文简介正在准备中。当前显示原文说明。

softaworks/agent-toolkit25712026年3月6日 更新

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

中文简介正在准备中。当前显示原文说明。

softaworks/agent-toolkit25712026年3月6日 更新

Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".

中文简介正在准备中。当前显示原文说明。

softaworks/agent-toolkit25712026年3月6日 更新

codex

免费

Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering.

中文简介正在准备中。当前显示原文说明。

softaworks/agent-toolkit25712026年3月6日 更新

This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.

中文简介正在准备中。当前显示原文说明。

softaworks/agent-toolkit25712026年3月6日 更新

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

中文简介正在准备中。当前显示原文说明。

softaworks/agent-toolkit25712026年3月6日 更新

查看 softaworks 的全部技能

报告此技能的问题