difficult-workplace-conversations
Structured framework for preparing, delivering, and following up on challenging workplace conversations.
- Three-phase approach covering preparation (clarify issue, check emotions, consider perspective), delivery (open neutrally, share perspective, listen actively, seek resolution), and followup (document agreements, check progress, maintain relationship)
- Includes the SBI model (Situation-Behavior-Impact) for framing feedback and guidance on managing your own emotions before difficult conversations
- Covers specific conversation types: performance feedback, conflict resolution, sensitive topics, and receiving feedback
- Provides opening scripts, anti-patterns to avoid, and escalation criteria for when conversations require management involvement
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)
More from softaworks/agent-toolkit
mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
4.0Khumanizer
|
3.9Kwriting-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
3.8Kqa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
3.7Kdatabase-schema-designer
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
3.7Kagent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
3.7K