
Feedback Mastery
Prepare and run constructive feedback or difficult 1:1 conversations with collaborators, contractors, or early teammates using Preparation–Delivery–Follow-up and SBI.
Overview
Feedback Mastery is an agent skill most often used in Grow (also Validate, Ship) that structures difficult conversations and constructive feedback using Preparation–Delivery–Follow-up and SBI.
Install
npx skills add https://github.com/softaworks/agent-toolkit --skill feedback-masteryWhat is this skill?
- Preparation–Delivery–Follow-up model for difficult conversations end-to-end
- Situation–Behavior–Impact (SBI) structure for specific, actionable feedback
- Guidance for 1:1s, conflicts, stakeholder expectation-setting, and receiving feedback well
- Read-only tooling (Read, Glob, Grep) for drafting scripts against existing notes or docs
- Preparation-Delivery-Follow-up three-part model
- Situation-Behavior-Impact (SBI) feedback technique
Adoption & trust: 3.7k installs on skills.sh; 2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to address behavior or performance without damaging trust or rambling in the moment.
Who is it for?
Indie builders who work with contractors, cofounders, or early hires and want scripted, respectful feedback before live conversations.
Skip if: Formal HR investigations, legal disputes, or crises that require licensed professionals rather than conversation frameworks.
When should I use this skill?
Preparing for difficult conversations, giving feedback, managing conflicts, or prepping sensitive 1:1s.
What do I get? / Deliverables
You leave with a prepared conversation outline, SBI-based feedback points, and a follow-up plan instead of an improvised confrontation.
- Conversation prep outline
- SBI-formatted feedback bullets
- Follow-up action checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf on Grow because sustained solo and indie builds eventually need clear communication with partners, users, and hires—not just code output. Support covers ongoing people issues (performance, conflict, expectations) that block delivery if left unaddressed.
Where it fits
Frame feedback to a cofounder when MVP scope keeps shifting without blaming them personally.
Prepare SBI notes before telling a contractor their PRs repeatedly miss acceptance criteria.
Plan a follow-up after a heated support handoff between you and a part-time CS helper.
Reset expectations with an ops freelancer after repeated missed incident response windows.
How it compares
Use instead of venting in chat when you need a repeatable feedback script aligned to behavioral facts.
Common Questions / FAQ
Who is feedback-mastery for?
Solo and indie builders who give or receive feedback with collaborators, contractors, or small-team members and want structured prep before sensitive talks.
When should I use feedback-mastery?
Use it when preparing 1:1 feedback, addressing missed expectations, mediating light conflict, or aligning stakeholders—e.g. after a Validate scope disagreement, before a Ship code-review tension, or during Grow support check-ins with a part-time contributor.
Is feedback-mastery safe to install?
It only declares Read, Glob, and Grep—no shell or network by default—but you should still review the Security Audits panel on this page before installing any skill.
SKILL.md
READMESKILL.md - Feedback Mastery
# Feedback Conversations ## Overview This skill provides frameworks for navigating difficult workplace conversations and delivering effective feedback. Whether you're addressing performance issues, resolving conflicts, or giving constructive feedback, these structured approaches lead to better outcomes. **Core insight:** Research shows that employees who approach difficult conversations with preparation and a clear framework are **60% more likely to reach a positive resolution** than those who engage without a plan. ## When to Use This Skill Use this skill when: - Preparing to give feedback to a colleague or direct report - Addressing performance issues or missed expectations - Navigating conflict between team members - Having 1:1 conversations about sensitive topics - Receiving feedback and wanting to respond constructively - Managing expectations with stakeholders **Keywords**: feedback, difficult conversation, 1:1, one-on-one, performance, conflict, expectations, behavior, confrontation ## Core Frameworks ### The Preparation-Delivery-Follow-up Model A three-part structure for difficult conversations: | Phase | Focus | Key Questions | | --- | --- | --- | | **Preparation** | Understand the issue, define goals, manage emotions | What's the problem? What outcome do I want? Am I calm? | | **Delivery** | Open neutrally, use facts not blame, encourage dialogue | How do I start? What evidence do I have? How do I involve them? | | **Follow-up** | Document actions, set check-ins, provide support | What did we agree to? When will we check in? How do I support? | ### The SBI Feedback Model **Situation-Behavior-Impact (SBI)** structures feedback to be specific, objective, and actionable: | Component | Description | Example | | --- | --- | --- | | **Situation** | Describe the specific context | "During yesterday's code review..." | | **Behavior** | State the observable action (not interpretation) | "...you interrupted Sarah three times while she was explaining her approach..." | | **Impact** | Explain the effect on team/project/person | "...which made her hesitate to share ideas and slowed down our discussion." | **Why it works:** SBI removes assumptions and focuses on observable facts, reducing defensiveness. ## Preparation Phase ### Step 1: Understand the Issue Ask yourself: - **What exactly is the problem?** (Be specific, not vague) - **How does it impact the team, project, or company?** - **Have I gathered all relevant facts?** - **Is this a pattern or a one-time event?** ### Step 2: Define Your Goals Before the conversation, clarify what you're seeking: | Goal Type | Example | | --- | --- | | Behavior change | "I want them to submit code reviews on time" | | Mutual understanding | "I want to understand what's blocking them" | | Expectation setting | "I want to clarify what 'done' means for features" | | Problem solving | "I want to find a solution together" | **Tip:** Use if-then statements to clarify stakes: > "If this behavior continues, then the project timeline will suffer, leading to missed deliverables." ### Step 3: Manage Your Emotions High emotional intensity reduces cognitive processing by 30%. Before the conversation: - [ ] Am I calm and in control? - [ ] Have I separated facts from personal frustrations? - [ ] Have I considered their perspective? - [ ] Can I present this without accusation? **Reframing technique:** | Accusatory | Constructive | | --- | --- | | "You always miss deadlines and it slows everyone down" | "I've noticed some recent delays and want to understand any challenges you're facing" | | "You never test your code proper