proto-persona

Overview of proto-persona skill

What proto-persona is for

The proto-persona skill helps you turn scattered research, market signals, and team knowledge into a working persona hypothesis. It is best for early-stage product, UX, and growth teams that need a usable target-user profile before full validation. If you want the proto-persona skill for UX Research, this is the right fit when your goal is alignment and direction, not proof.

When this skill is the right choice

Use proto-persona when you have partial evidence: a few interviews, support themes, analytics, competitor patterns, or stakeholder insight. It is useful when teams keep debating “who are we building for?” and need a structured starting point. It is not a generic persona prompt; it is designed to make assumptions visible so they can be tested later.

What makes it different

The core value of proto-persona is speed with traceability. You get a concise persona framework that captures likely traits, pains, goals, and influences without pretending the profile is validated. That makes the output more decision-friendly than an ad hoc brainstorming prompt, especially when you need to spot research gaps and avoid design-by-committee.

How to Use proto-persona skill

Install the skill

For a local skill install, use the repo command in the upstream docs: npx skills add deanpeters/Product-Manager-Skills --skill proto-persona. After install, confirm the skill folder is available at skills/proto-persona and that SKILL.md and template.md are present before you start drafting.

Feed it the right inputs

A strong proto-persona prompt should include the problem space, known audience signals, and any constraints. Good inputs look like: product category, target market, stage of company, evidence you already have, and the decision the persona must support. For example: “Create a proto-persona for a B2B analytics app aimed at operations managers in mid-market SaaS; use 6 support tickets, 2 customer calls, and competitor positioning as input.”

Suggested workflow

Start by reading SKILL.md, then template.md, then examples/sample.md to understand the expected structure and level of specificity. Use those files to map your rough notes into the template’s sections: name, bio, quotes, pains, goals, and attitudes/influences. If your source material is thin, label assumptions clearly instead of filling gaps with invented certainty.

Practical tips for better output

Keep the prompt anchored to one persona and one job-to-be-done. State whether you want a single proto-persona or multiple segments, because mixing them usually weakens the result. Include facts that matter to adoption decisions, such as buying authority, use context, and known objections. If you are using proto-persona usage as part of a broader research workflow, ask for explicit “assumption vs. evidence” separation so your team can validate it later.

proto-persona skill FAQ

Is proto-persona validated research?

No. The proto-persona guide is for hypothesis building, not final segmentation. It is useful when you need a fast working model, but it should not replace interviews, surveys, or behavioral analysis when the decision is high stakes.

How is this different from a normal prompt?

A normal prompt can produce a persona, but the proto-persona skill gives you a clearer structure and a better fit for early product work. It pushes you toward the inputs that matter, the template fields that support team alignment, and the reminder that the output is provisional. That usually makes the result easier to review and revise.

Is it beginner-friendly?

Yes, if you can provide a few real signals about your audience. You do not need a mature research program to use proto-persona, but you do need enough context to avoid generic output. Beginners get the best results when they start with one narrow use case and one clear segment.

When should I not use it?

Do not use proto-persona when you need statistically grounded personas, when the audience is already well-researched, or when the team is still deciding the product category itself. In those cases, the proto-persona skill may add structure, but it will not solve the underlying uncertainty.

How to Improve proto-persona skill

Give stronger evidence, not more words

The biggest quality jump comes from better inputs: interview notes, top support themes, analytics patterns, sales objections, and competitor observations. A weak prompt says “our users are busy professionals”; a stronger one says “time-poor operations managers in 100-500 employee SaaS firms who ask for integrations, proof of ROI, and low setup effort.” That kind of detail improves the proto-persona skill output immediately.

Separate assumptions from facts

Tell the skill which points are observed and which are inferred. This matters because proto-personas are only useful when teams can see what still needs validation. If you blur evidence and guesswork, the output can look polished while quietly hiding risk.

Iterate against a real decision

After the first draft, ask what would change your roadmap, messaging, or research plan. Then revise the inputs around those decisions, not around wording alone. The best proto-persona install-and-use loop is: draft, challenge the assumptions, add missing evidence, and regenerate the persona with a narrower focus.

Watch for common failure modes

The most common problems are generic demographics, too many goals, and persona traits copied from the product team’s preferences instead of user signals. If the result feels vague, add constraints from the target workflow, buying context, and pain severity. For proto-persona for UX Research, the most useful improvement is often a sharper list of validation questions the persona now raises.