plugins/pm-people/skills/360-feedback-template/SKILL.md
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
npx skillsauth add mohitagw15856/pm-claude-skills 360-feedback-templateInstall 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.
This skill produces two outputs depending on what the user needs: (1) a complete 360 survey instrument for gathering feedback, or (2) a structured 360 feedback report written from gathered notes. Both outputs follow best practice: behaviourally anchored ratings, specific examples, and development-oriented framing.
Ask the user which output they need, then gather inputs:
For a survey instrument:
For a feedback report:
Purpose: This survey helps [Name / "the reviewee"] understand how their behaviours and impact are perceived by the people they work with most closely. Responses [are / are not] anonymous. Results will be shared as [individual responses / aggregated themes].
Instructions: For each statement, rate how frequently you observe this behaviour. Add specific examples in the open-ended sections — these are the most valuable part of the survey.
Rating scale:
| Statement | Rating (1–5) | |---|---| | Delivers work on time and to the expected quality | | | Proactively flags risks and blockers before they become problems | | | Follows through on commitments without needing to be chased | | | Manages their workload effectively without compromising quality | | | Adapts quickly when priorities or requirements change | |
Open question: Describe a specific time when [Name] handled a delivery challenge particularly well or poorly.
| Statement | Rating (1–5) | |---|---| | Communicates clearly and concisely in both written and verbal formats | | | Listens actively and considers others' input before responding | | | Keeps the right people informed without over-communicating | | | Resolves disagreements constructively and without defensiveness | | | Makes it easy for others to collaborate with them | |
Open question: Give an example of how [Name] handled a difficult or high-stakes communication.
| Statement | Rating (1–5) | |---|---| | Sets a clear direction that others can follow | | | Builds confidence and capability in people around them | | | Influences decisions without relying on authority | | | Gives clear, constructive feedback that helps others improve | | | Creates an environment where people feel safe to raise concerns | |
Open question: Describe a situation where [Name]'s leadership had a notable positive or negative impact on the team.
| Statement | Rating (1–5) | |---|---| | Understands the broader business context, not just their immediate work | | | Makes connections between their work and organisational goals | | | Thinks ahead and anticipates second-order consequences | | | Brings original ideas or new approaches to problems | | | Balances short-term needs with longer-term thinking | |
Open question: Give an example of [Name] demonstrating (or missing) strategic thinking.
| Statement | Rating (1–5) | |---|---| | Treats everyone with respect, regardless of level or background | | | Is someone people trust and can rely on | | | Gives credit to others and shares the spotlight | | | Takes responsibility for mistakes without placing blame | | | Contributes positively to team morale, especially under pressure | |
Open question: How does [Name] embody (or not embody) the team's values in practice?
Open questions (all reviewers):
What is [Name]'s single most important strength? Give a specific example.
What is the one behaviour or habit that, if changed, would most increase [Name]'s effectiveness?
Is there anything else you want [Name] to know? (This response will be shared directly.)
Review cycle: [Quarter / Year / Promotion cycle] Responses received: [X total — X peers, X direct reports, X managers, X cross-functional] Report prepared by: [HR / People team / Manager / Coach] Date: [Date]
This report synthesises feedback from [X] reviewers. Open-ended responses have been lightly edited for clarity; no individual response is attributed to protect reviewer confidentiality. Direct quotes marked in italics appear verbatim.
[3–4 sentences. State the overall picture: what is this person known for, what is working well, and what one or two areas are the consistent development themes. Balanced, honest, and grounded in the data — not a sanitised summary.]
Overall rating: [X.X / 5.0 — above average / at level / below expectations for level]
Theme 1: [Strength — e.g. Reliability and follow-through]
[2–3 sentences synthesising the feedback evidence for this strength. Reference how many reviewers noted it and in what contexts.]
"[Direct quote from reviewer that best illustrates this theme]"
Theme 2: [Strength — e.g. Collaborative problem-solving]
[2–3 sentences synthesising evidence.]
"[Direct quote]"
Theme 3: [Strength — e.g. Clear communication under pressure]
[2–3 sentences synthesising evidence.]
"[Direct quote]"
Theme 1: [Development area — e.g. Giving timely upward feedback]
[2–3 sentences describing the behaviour pattern observed, what impact it has, and what different looks like. Non-blaming and specific.]
"[Direct quote that captures the theme]"
Suggested actions:
Theme 2: [Development area — e.g. Strategic communication to leadership]
[2–3 sentences.]
"[Direct quote]"
Suggested actions:
| Competency | Average score | Range | Notable pattern | |---|---|---|---| | Delivery & Execution | [X.X] | [X–X] | [e.g. Consistently high; one outlier] | | Communication & Collaboration | [X.X] | [X–X] | [e.g. Peers score higher than direct reports] | | Leadership & Influence | [X.X] | [X–X] | [...] | | Strategic Thinking | [X.X] | [X–X] | [...] | | Culture & Values | [X.X] | [X–X] | [...] | | Overall | [X.X] | [X–X] | |
Score variance: [Is there high agreement or wide spread across reviewers? High variance suggests the behaviour is context-dependent — explore when and with whom.]
[Include up to 3 unedited quotes from the "Is there anything else you want [Name] to know?" question. These are shared verbatim as agreed in the survey instructions.]
"[Quote 1]"
"[Quote 2]"
"[Quote 3]"
[1–2 specific, measurable development commitments. Written to be agreed in the feedback conversation — not prescriptive.]
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.