proto-persona

Create a proto-persona canvas from existing research, market signals, and team knowledge.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill proto-persona-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: proto-persona
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/proto-persona
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill proto-persona-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often argue from private mental models of the customer before real research exists. This Skill turns scattered research notes, support transcripts, analytics, and team knowledge into a structured proto-persona hypothesis that aligns the team early and makes evidence gaps visible. ## Core Features & Use Cases - Facilitated persona building: Asks up to four targeted questions one at a time, accepts bulk research drops, and reports what was found, inferred, and still missing. - Evidence discipline: Forces every quote to be sourced or marked as a placeholder, and tags every unverified claim with [ASSUMPTION - VALIDATE] so nothing fabricated slips into decks. - Stable output contract: Emits the Proto Persona Canvas template with fixed section names that paste cleanly into design docs and Jira, plus an optional anti-persona for scoping. - Use Case: A product team preparing a discovery phase pastes three support call transcripts and receives a labelled proto-persona with real quotes, tagged assumptions, and interview questions to validate them. ## Quick Start Ask the assistant to build a proto-persona for your target user from your existing research notes and support transcripts.

Frequently Asked Questions about proto-persona

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

FAQPage Schema
How do I create a proto-persona before doing user research?▼

Gather whatever evidence exists, such as support transcripts, analytics, and team knowledge, then build a hypothesis persona with every unevidenced field tagged as an assumption or placeholder. The result aligns the team and defines what to validate next.

What is the difference between a proto-persona and a validated persona?▼

A proto-persona is built in hours from assumptions plus limited research and evolves rapidly, while a validated persona comes from extensive primary research over weeks. A proto-persona graduates when pains, job, and at least two quotes come from research with more than five participants.

Can I use a proto-persona instead of talking to users?▼

No. A proto-persona is a labelled hypothesis that tells you what to go ask users, not a replacement for research. It should carry a visible proto status until its load-bearing claims are validated through primary research.

Why should persona quotes never be invented?▼

A fabricated quote is indistinguishable from a real one once it enters a slide deck and will be repeated for years as false evidence. The rule is to use verbatim research quotes or an explicit placeholder stating what you would ask to fill the gap.

When should I add an anti-persona to my persona work?▼

Add an anti-persona when scope creep is a risk, because naming who the product is explicitly not for kills more scope creep than prioritisation frameworks. It defines who you are not building for in v1 and what signal would make you reconsider.