Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
A structured framework for approaching challenging workplace conversations including conflicts, performance issues, sensitive feedback, and emotionally charged discussions.
Difficult conversations succeed or fail based on three phases:
Purpose: Set yourself up for a productive conversation
Clarify the Issue
Check Your Emotions
Consider Their Perspective
Define Your Goal
Purpose: Have the conversation effectively
Open Neutrally
Share Your Perspective
Listen Actively
Seek Resolution
Purpose: Ensure lasting resolution
Document Agreements
Check Progress
Maintain Relationship
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.
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?
| 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 |
Escalate when:
feedback-mastery skill - SBI feedback model (overlaps but more feedback-focused)professional-effective-communication skill - General communication patterns**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."
**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."
**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."
A successful difficult conversation:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.