skills/giving-feedback/SKILL.md
Turn a vague concern into specific, kind, actionable feedback. Use when asked to give feedback, write a feedback note, prepare to tell someone something hard about their work, or coach a report/peer. Produces ready-to-deliver feedback structured on situation–behaviour–impact, separating observation from judgement, with the change requested and an opening line — calibrated to praise or constructive.
npx skillsauth add mohitagw15856/pm-claude-skills giving-feedbackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Most feedback is useless because it's vague ("be more proactive"), judgemental ("you're careless"), or sandwiched into mush. Good feedback is specific, describes behaviour not character, names the impact, and makes the ask clear. This skill turns a fuzzy concern into feedback the person can actually act on — delivered with enough care that they hear it.
Ask for these only if they aren't already provided:
1. The core (SBI) — the spine of good feedback:
2. The ask — for constructive: the specific change ("next time, walk the pricing slide before Q&A"). For praise: name what to keep doing and why it mattered (praise that's specific gets repeated).
3. Opening line — how to start so they're ready to hear it (ask permission / state intent: "Can I share something from the review? I want the next one to land even better.").
4. Make it a dialogue — 1–2 questions to invite their view ("How did it feel from your side?"), because feedback is a conversation, not a verdict.
Calibration note — keep it timely (soon, not saved for the review), private if constructive, and about the behaviour, never the person.
SBI feedback model (Center for Creative Leadership) and Radical Candor (Kim Scott) — care personally, challenge directly.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.