- Home
- Skills
- Softaworks
- Agent Toolkit
- Feedback Mastery
feedback-mastery_skill
- Python
273
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill softaworks/agent-toolkit --skill feedback-mastery- README.md9.7 KB
- SKILL.md11.3 KB
Overview
This skill teaches structured approaches to navigate difficult workplace conversations and deliver constructive feedback. It centers on the Preparation-Delivery-Follow-up model and the Situation-Behavior-Impact (SBI) technique to make feedback specific, objective, and actionable. Use it to reduce defensiveness, clarify expectations, and drive measurable behavior change.
How this skill works
The skill walks you through three phases: prepare by gathering facts, defining goals, and regulating emotion; deliver using neutral openings, factual examples, and SBI structure; and follow up with documented actions and scheduled check-ins. It provides scripts, prompts, and checklists for common scenarios like performance issues, interpersonal conflict, and stakeholder misalignment. The approach emphasizes observable behavior, impact statements, and collaborative problem solving.
When to use it
- Before delivering performance or behavioral feedback to a colleague or direct report
- When mediating conflict between team members or facilitating a tough 1:1
- When aligning expectations with stakeholders about scope, timelines, or quality
- When receiving feedback and wanting to respond constructively
- When documenting and tracking agreed changes after a difficult conversation
Best practices
- Prepare with concrete examples and a clear, measurable goal for the conversation
- Open neutrally, present facts not judgments, and avoid global labels like "always" or "never"
- Use the SBI model: describe the Situation, the observable Behavior, and the Impact
- Invite the other person’s perspective and co-create solutions rather than issuing ultimatums
- Document agreed actions, set check-in dates, and celebrate progress to reinforce change
Example use cases
- Addressing repeated release delays by reviewing recent PRs, timelines, and blockers
- Giving a developer constructive feedback after a code review that introduced regressions
- Resolving a disagreement over technical approach by meeting separately then facilitating a joint discussion
- Pushing back on unrealistic leadership deadlines by presenting trade-offs and proposed options
- Responding calmly when receiving critical feedback by asking for specific examples and follow-up
FAQ
Provide the smallest concrete context (date, meeting, PR) and the observable action. Specificity reduces ambiguity and defensiveness.
What if the other person becomes defensive?
Pause, acknowledge their feelings, restate your intent to find a solution, and ask clarifying questions to re-center the dialogue.