_project-evaluation-user

Evaluate deliverables for user-facing issues using defined evaluation lenses.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/HahyeonJeon/gobbi --skill project-evaluation-user
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _project-evaluation-user
Source: https://github.com/HahyeonJeon/gobbi/tree/main/plugins/gobbi/skills/_project-evaluation-user
Command: npx skills add https://github.com/HahyeonJeon/gobbi --skill project-evaluation-user

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured lens to evaluate whether a deliverable truly meets user needs by centering the perspective of the person who will use it, rather than focusing on internal quality alone.

Core Features & Use Cases

  • Provides evaluation scopes like Immediate Usability, Friction, Understandability, and Workflow Impact to surface user-facing issues.
  • Useful for product teams, UX researchers, and QA to generate actionable, user-facing feedback and improvements.
  • Use case: when reviewing a software release or documentation, apply this perspective to ensure it reduces friction and communicates clearly to end users.

Quick Start

Load this skill and run it on the deliverable from the user's viewpoint.

Frequently Asked Questions about _project-evaluation-user

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate a deliverable from the user perspective?

To evaluate a deliverable from the user perspective, apply structured lenses like Immediate Usability, Friction, Understandability, and Workflow Impact to identify user-facing issues and generate actionable recommendations.

What is the best way to review UX friction in project outputs?

The best way to review UX friction in project outputs is to enforce evaluation against defined user-centered lenses, surfacing concrete observations about workflow impact and immediate usability rather than focusing on internal quality alone.

How do I generate actionable user-facing feedback for documentation?

To generate actionable user-facing feedback for documentation, evaluate the deliverable against understandability and friction scopes to ensure it communicates clearly and reduces end-user friction.

Can I use this approach to evaluate software implementations and configurations?

Yes, you can evaluate software implementations and configurations by applying this perspective to project outputs, ensuring interfaces and configurations are assessed from the end-user viewpoint to surface concrete user-facing issues.

When do I need to apply user-centered evaluation lenses to a project deliverable?

You need to apply user-centered evaluation lenses when reviewing a deliverable like a software release or interface to ensure it truly meets user needs, reduces workflow friction, and communicates clearly to end users.

What is the difference between internal quality review and user-centered evaluation?

Internal quality review focuses on technical correctness, while user-centered evaluation centers on the person who will use the deliverable, assessing immediate usability, friction, understandability, and workflow impact to provide actionable user-facing improvements.