qa-persona-testing
Installation
SKILL.md
QA Persona Testing
Test a solution or app as a specific person from a specific group — an Ideal Customer Profile (ICP) or defined user segment — rather than as a QA engineer. The skill covers the full loop: find the profile (using sibling skills), set the persona up as an executable specification, drive the app through browser automation like that person would, and produce an improvement report with what to fix, what to avoid, and what to keep.
This is persona simulation, not E2E test authoring. It finds friction, confusion, trust breaks, and abandonment; it does not replace assertion-based regression tests (qa-testing-playwright) or research with real users (software-ux-research).
Quick Reference
| Task | Read or use | Outcome |
|---|---|---|
| Find/derive the ICP or persona group | ## Phase 1 — DEFINE + sibling skills table |
Evidence-backed persona candidates |
| Turn a persona into an executable spec | assets/persona-profile.md + references/persona-construction.md | Persona profile with behavioral traits and scenario pack |
| Run a browser test session as the persona | references/browser-execution.md | Filled assets/session-log.md per scenario |
| Keep the simulation honest (anti-sycophancy) | references/persona-construction.md | Persona that abandons, complains, and stays in character |
| Write the improvement report | assets/findings-report.md + references/reporting-and-validity.md | Ranked findings, prioritized fixes, validity caveats |
| Decide what simulation can and cannot claim | references/reporting-and-validity.md | Correctly-hedged conclusions |