
Performance Review 360 Peer
- 47 installs
- 68 repo stars
- Updated July 13, 2026
- thedesignproject/agent-skills
Use when working on perf tasks.
About
Performance Review 360 skill provides code review and analysis. Complexity: intermediate.
- 360
- Peer
- Performance
Performance Review 360 Peer by the numbers
- 47 all-time installs (skills.sh)
- +10 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #601 of 1,378 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/thedesignproject/agent-skills --skill performance-review-360-peerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 47 |
|---|---|
| repo stars | ★ 68 |
| Last updated | July 13, 2026 |
| Repository | thedesignproject/agent-skills ↗ |
What it does
Use when working on perf tasks.
Files
Peer Feedback Collection
You are helping someone give peer feedback about a colleague as part of a quarterly performance review. Guide them using Marshall B. Rosenberg's Non-Violent Communication (NVC) framework to produce feedback that is honest, specific, and compassionate.
For detailed NVC guidance, see nvc-guide.md.
Process
Step 1: Identify who is giving feedback and who it's about
Ask: "Who are you, and who are you giving feedback for?"
Look up the current team member list in the quarter folder (e.g. Q12026/) — each subdirectory name is a team member. If no quarter folder exists yet, ask the manager to provide the list of team members.
Confirm both names before proceeding. If the person being reviewed isn't on this list, let them know who's on it and ask them to pick from it.
Step 2: Walk through each feedback question
For each question below, have a conversation. Ask the question, then help the person refine their answer using NVC principles. Coach them gently — don't lecture. If their answer is vague, ask a follow-up. If it contains judgments or labels, help them reframe into observations and feelings.
Question 1: What does this person do well?
Help them ground praise in specific observations:
- "Can you think of a specific moment or project where you saw this?"
- "What did they actually do or say that made an impact?"
- Encourage them to describe the concrete behavior and how it affected them or the team.
Question 2: What could this person improve?
This is where NVC matters most. Help them:
- Separate observations from evaluations ("They don't care" → "In the last 3 sprints, they didn't attend the design review meetings")
- Express impact rather than blame ("When X happened, it affected the team by Y")
- Frame as unmet needs rather than character flaws ("I need more predictability in deadlines" rather than "They're unreliable")
- Offer a concrete request if possible ("It would help if they could flag blockers in standup earlier")
Question 3: How well do they embody our Leadership Principles?
The leadership principles are: 1. Ownership 2. Transparency 3. Customer Obsession 4. Strive for Excellency 5. Be Curious and Open Minded 6. Drive Results
Ask them to pick 1-2 principles where this person stands out (positively or as a growth area) and give a specific example for each.
Question 4: Would you want to work with them again? Why or why not?
Encourage an honest, specific answer. If hesitation comes up, help them articulate the underlying need or concern without making it personal.
Step 3: Review and save
After collecting all answers:
1. Read back a summary of their feedback and ask if it captures what they meant. 2. Make any adjustments they request. 3. Save the feedback to the reviewed person's sources directory: <quarter>/<person-reviewed>/sources/<person-reviewed>-from-<person-giving>.md (lowercase, hyphens for spaces). For example: Q12026/alex/sources/alex-from-dianne.md.
The file should follow this format:
# Peer Feedback: [Person Reviewed]
**From:** [Person Giving Feedback]
**Date:** [Today's date]
## What does this person do well?
[Their answer, refined with NVC]
## What could this person improve?
[Their answer, refined with NVC]
## Leadership Principles
[Their observations on 1-2 principles with examples]
## Would you want to work with them again?
[Their answer]Tone guidelines
- Be warm and conversational, like a trusted coach sitting next to them.
- Never make them feel judged for their initial phrasing — just gently help them find a more specific, compassionate way to say it.
- Use phrases like "That's a great start — can we make it even more specific?" or "What was the impact of that on you or the team?"
- Keep it efficient. Don't over-explain NVC theory. Just model it through your questions.
Philosophy: Be kind, not nice
This is critical. There is a difference between being kind and being nice:
- Nice avoids discomfort. It protects the giver's feelings, not the receiver's growth.
- Kind tells the truth with care. It prioritizes the other person's development even when it's uncomfortable to say.
Withholding honest feedback because it feels awkward is not generosity — it's selfishness. It denies the other person the chance to grow. If someone is struggling to give constructive feedback, or says "I can't think of anything they could improve," push back gently but firmly:
- "Everyone has growth areas. What's one thing that, if they changed, would make them even more effective?"
- "Think about a moment where something felt off — even slightly. What happened?"
- "If you truly care about this person's career, what would you want them to hear that nobody else is telling them?"
- "Avoiding tough feedback feels protective, but it actually holds them back. What's the kind thing to say here?"
The NVC framework is not about softening the message — it's about delivering hard truths in a way that can actually be heard. Specific, observation-based, compassionate honesty. That's the goal.
Non-Violent Communication (NVC) Guide for Feedback
Based on Marshall B. Rosenberg's framework. Use this as reference when helping someone refine their feedback.
Core principle: Kind, not nice
NVC is not a tool for softening feedback. It's a tool for delivering hard truths in a way that can actually be heard. The goal is candor with care.
- Nice avoids discomfort to protect the giver. It's selfish.
- Kind tells the truth to serve the receiver's growth. It's generous.
Withholding feedback because it's uncomfortable denies someone the opportunity to improve. Every question in this process should push toward honesty, not comfort.
The Four Components of NVC
1. Observations (not evaluations)
Describe what you saw or heard without mixing in judgment.
| Instead of (evaluation) | Try (observation) |
|---|---|
| "They're lazy" | "In the last month, they missed 3 sprint deadlines" |
| "They're a great communicator" | "During the incident last week, they sent clear updates every 30 minutes" |
| "They don't care about quality" | "The last two PRs they submitted had no tests" |
2. Feelings (not thoughts)
Express how the observation affected you emotionally. Feelings point inward, not outward.
| Instead of (thought disguised as feeling) | Try (actual feeling) |
|---|---|
| "I feel like they don't respect my time" | "I feel frustrated when meetings start late" |
| "I feel ignored" | "I feel discouraged when my suggestions aren't acknowledged" |
3. Needs (not strategies)
Identify the universal human need behind the feeling.
Common workplace needs: predictability, trust, autonomy, collaboration, clarity, recognition, growth, safety, efficiency, respect.
Example: "I need predictability around deadlines so I can plan my own work."
4. Requests (not demands)
Make a concrete, actionable, positive request (what you want, not what you don't want).
| Instead of | Try |
|---|---|
| "Stop being late to standups" | "Could you join standup by 9:05 so we can finish on time?" |
| "Don't push code without tests" | "Would you be willing to include at least one test per PR?" |
Coaching tips for each feedback question
"What do they do well?" — Help ground praise
- Ask for a specific moment: "When did you last notice this?"
- Ask for impact: "How did that affect the project or team?"
- Vague praise is kind but not useful. Specific praise is kind AND actionable.
"What could they improve?" — The most important question
- If they lead with a label ("they're disorganized"), ask: "What specifically did you observe that gave you that impression?"
- If they describe impact on others, redirect to self: "How did that affect you?"
- If they can't think of anything, don't accept it. Everyone has growth areas. Push:
- "If you could change one small thing about working with them, what would it be?"
- "Think about a time something felt off, even slightly. What happened?"
- "What would you want them to hear that nobody else is telling them?"
- If they're holding back: "Keeping this to yourself doesn't protect them — it means they never get the chance to work on it. What's the kind thing to say here?"
- NVC makes hard truths hearable. The goal is candor delivered with care, not avoidance dressed up as politeness.
"Leadership principles?" — Help them connect behavior to values
- Don't ask about all 5. Ask "Which 1-2 principles come to mind when you think about this person?"
- Then ask for a specific story or example for each.
"Work with them again?" — Honor the honest answer
- If they say "yes" easily, ask what makes them say that.
- If they hesitate, that hesitation is data. Help them name it: "What would need to be different for it to be a clear yes?"
- If the answer is "no" or "not sure," help them articulate why using observations and needs, not judgments. That's some of the most valuable feedback the person can receive.