user-advocate

Evaluate feature desirability and livability from the end user's perspective.

10|11|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/microsoft/amplifier-bundle-skills --skill user-advocate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-advocate
Source: https://github.com/microsoft/amplifier-bundle-skills/tree/main/skills/user-advocate
Command: npx skills add https://github.com/microsoft/amplifier-bundle-skills --skill user-advocate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate features from the perspective of the person who will actually live with them, instead of the builder or the demo. It is useful when a proposal looks clever or feasible but may not be wanted, may be frustrating in practice, or may leave the real user stranded when things go wrong.

Core Features & Use Cases

  • Desirability Review: Distinguish between something that can be built and something the served person actually asked for.
  • Livability Review: Check whether the experience still works for tired, rushed, confused, or edge-case users after the happy path.
  • Interface Consumer Lens: Apply the same questions to APIs, CLIs, and libraries by treating the consumer as the user.
  • Use Case: Review a cancellation flow, internal API, or feature proposal and ask whether the real person needs it, can understand it, and can recover from mistakes without being trapped.

Quick Start

Ask the user-advocate skill to evaluate this feature from the perspective of the person who will use it and identify where the design is buildable but not actually wanted.

Frequently Asked Questions about user-advocate

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

FAQPage Schema
What is a user advocate evaluation for product features?

A user advocate evaluation assesses whether a feature is actually wanted by the person who will use it and if they can comfortably live with the experience. It judges desirability, recovery paths, edge cases, and user-facing friction rather than technical breakage.

How do I review an API or CLI from the consumer's perspective?

Review an API or CLI by treating the consumer as the real user. Evaluate whether the interface consumer can understand the design, needs the functionality, and can recover from mistakes without being trapped during edge cases.

How do I evaluate feature desirability versus buildability?

Evaluate feature desirability by distinguishing between something that can be built and something the served person actually asked for. This review prevents implementing clever or feasible proposals that may not be wanted or are frustrating in practice.

What is a livability review for UX design?

A livability review checks whether an experience still works for tired, rushed, confused, or edge-case users after the happy path. It ensures real users can navigate cancellation flows or error states without being stranded when things go wrong.

Can I use this evaluation method for debugging and implementation review?

Yes, you can apply this evaluation to product planning, design review, implementation review, and debugging. It focuses on identifying user-facing friction and recovery paths rather than checking for technical breakage or builder convenience.

When should I not focus on technical breakage during a product review?

You should shift focus away from technical breakage when a proposal looks feasible but may leave the real user stranded. Prioritize evaluating desirability and user-facing friction to ensure the experience works for edge-case users recovering from mistakes.