adversarial-ux-test

Roleplay a difficult user to surface UX friction and generate prioritized tickets.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill adversarial-ux-test-anandaanugrahhandyanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-ux-test
Source: https://github.com/AnandaAnugrahHandyanto/savarez_agent/tree/main/optional-skills/dogfood/adversarial-ux-test
Command: npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill adversarial-ux-test-anandaanugrahhandyanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roleplay the most difficult, tech-resistant user for your product — identify every UX pain point and translate them into actionable tickets for your team.

Core Features & Use Cases

  • Adversarial persona-based exploration to surface usability friction across core flows
  • Pragmatism filter that classifies feedback into real issues, improvements, or feature requests
  • Automatic generation of tickets with verbatim quotes, issue descriptions, and suggested fixes

Quick Start

Run an adversarial UX test on your staging URL to uncover friction and generate tickets.

Frequently Asked Questions about adversarial-ux-test

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

FAQPage Schema
How do I generate actionable UX tickets from user testing feedback?

You can generate actionable UX tickets by running an adversarial test that roleplays a difficult, tech-resistant user, filtering feedback through a pragmatism layer to separate real friction from noise, and converting genuine issues into prioritized tickets with quotes and suggested fixes.

What is adversarial UX testing and how does it surface friction?

Adversarial UX testing is a technique that roleplays the most difficult, tech-resistant user to explore core flows and surface usability friction, identifying real pain points rather than expected behaviors to expose hidden design flaws.

How do I separate real UX issues from feature requests during QA?

You can separate real UX issues from feature requests by passing raw user feedback through a pragmatism filter that classifies comments into real issues, improvements, or feature requests, ensuring only genuine friction becomes an actionable ticket.

Can I run an adversarial persona test on a staging URL to find usability problems?

Yes, you can run an adversarial persona-based exploration on a staging URL to uncover friction across core flows, automatically generating ticket-ready items containing verbatim user quotes, issue descriptions, and suggested fixes for your team.

Does adversarial testing work for surfacing pain points in dogfooding?

Adversarial testing works for dogfooding by simulating a highly tech-resistant user to aggressively probe your core flows, exposing genuine UX pain points and translating them into prioritized, actionable tickets for developers.

What is the best way to convert user quotes into prioritized development tickets?

The best way to convert user quotes into prioritized development tickets is to use a pragmatism layer that filters roleplay feedback, classifying the verbatim quotes into actionable issues with descriptions and suggested fixes for your team.