Peer Feedback via NVC: A Skill for Developers

Where this fits

You're a developer who needs to write peer feedback for a colleague's quarterly review. You want to be honest about friction points, but you're worried about sounding harsh or damaging the relationship. This skill—performance-review-360-peer—walks you through the Non-Violent Communication (NVC) framework, turning your raw observations into feedback that is specific, compassionate, and actionable. It fits directly into the review workflow, whether you're a team lead or an individual contributor.

Why agents benefit

• Structured coaching: The agent doesn't just collect answers; it guides you through each NVC component (observation, feeling, need, request) with targeted questions, ensuring your feedback is balanced.
• Context-aware roster validation: It checks the quarter folder for team member names, preventing feedback for someone outside the team or with a misspelled name.
• Iterative refinement: The agent asks follow-up questions to help you move from vague statements like "they're often late" to concrete, non-judgmental observations like "In the last sprint, they joined standup 10 minutes late on three occasions."
• Empathy enforcement: It gently redirects you when you slip into blame or evaluation, keeping the feedback aligned with NVC principles.
• Time-saving template: Instead of staring at a blank form, the agent provides a repeatable process that fits any peer review scenario.

Practical scenarios

Quarterly review with a difficult colleague

You need to address a pattern of missed deadlines without causing defensiveness. The agent helps you frame it as an observation ("The last two deliverables were submitted after the agreed date"), connect it to a feeling ("I felt anxious about the project timeline"), and make a request ("Can we agree on a mid-sprint check-in to catch delays earlier?").

Onboarding feedback for a new hire

You're reviewing a junior developer who is eager but often asks for help before trying to solve problems independently. The skill guides you to acknowledge their enthusiasm while suggesting a specific need (e.g., "I need to see you attempt a debugging step first") without sounding condescending.

Remote team feedback across time zones

When working asynchronously, you might only see Slack messages and PR comments. The agent helps you base feedback on observable artifacts, like "Your PR descriptions often lack context, which made it hard for me to review"—turning a potential personality clash into a process improvement.

Add it to your agent workflow

Install the skill directly from your agent's CLI:

npx skills add thedesignproject/agent-skills --skill performance-review-360-peer

Then invoke it with a prompt like: "I need to give peer feedback for Maria in Q12026. Help me structure it using NVC." The agent will ask for your name and the reviewee, verify the team roster, and walk through the five feedback questions step by step.

Compare before adopting

Before you commit, evaluate this skill against alternatives. Check the quality of the NVC guide it references—does it match Rosenberg's original framework? Look at the repository's maintenance freshness (last commit, issue responses). Compare with generic feedback templates or other skills that might not enforce NVC as strictly. Also consider your workflow: does your team use a quarter folder structure? If not, you'll need to adapt the skill's assumptions.

Why it is worth tracking

With 86 stars and an active author, this skill shows early community traction. It solves a real pain point—peer feedback that is both honest and kind—and its process is repeatable. Track it to see if the author adds more NVC resources or integrates with HR tools. Re-evaluate after a few months: if the repo stays updated and the skill gains more adopters, it's a solid addition to your agent's productivity toolkit. For more details, see the skill page on OpenAgentSkill.