proto-persona

Create a proto-persona document from research, market signals, and stakeholder knowledge.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/tabooes/pm_skills --skill proto-persona-tabooes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proto-persona
Source: https://github.com/tabooes/pm_skills/tree/main/skills/proto-persona
Command: npx skills add https://github.com/tabooes/pm_skills --skill proto-persona-tabooes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proto-personas provide a fast, hypothesis-driven customer profile to align teams early in product development, especially when formal user research is pending.

Core Features & Use Cases

  • Assumption-based persona: quick starter profile synthesized from existing research, market signals, and stakeholder knowledge.
  • Gap identification: highlights missing context and validation needs to guide research.
  • Template-driven outputs: produces a reusable proto-persona scaffold that can evolve into validated personas.

Quick Start

Generate a proto-persona draft from current project context and provide a ready-to-review profile.

Frequently Asked Questions about proto-persona

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

FAQPage Schema
What is a proto-persona and when do I need one for product development?

A proto-persona is an assumption-based customer profile synthesized from stakeholder knowledge and market signals. You need it during early product development to quickly align teams and identify gaps when formal user research is pending.

How do I create a proto-persona from existing project context?

To create a proto-persona, synthesize current research, market signals, and stakeholder knowledge into a standard template. This generates a ready-to-review profile containing demographics, pains, goals, and attitudes to guide initial design decisions.

Proto-persona vs validated persona: which approach fits early product alignment?

Proto-personas fit early product alignment best by providing a fast, hypothesis-driven scaffold without formal research. Validated personas require completed user research, making proto-personas the quicker category-level alternative for initial team alignment.

Can I use a proto-persona template to identify user research gaps?

Yes, you can use a proto-persona template to identify user research gaps. The generated profile highlights missing context and validation needs, directly guiding where formal user research should focus next.

What sections are included in a standard proto-persona document?

A standard proto-persona document includes sections for Name, Bio & Demographics, Quotes, Pains, What is This Person Trying to Accomplish, Goals, and Attitudes & Influences. These fields structure the assumption-based profile for team review.

What are the limitations of using assumption-based personas?

Assumption-based personas lack formal user research validation and rely on stakeholder knowledge. They should not replace validated personas but serve as a temporary scaffold to guide early design decisions and highlight missing context.