proto-persona

Create hypothesis-driven proto-persona profiles from research, market signals, and team knowledge.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill proto-persona-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: proto-persona
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/2-discovery/proto-persona
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill proto-persona-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Early-stage product teams often lack validated user research but still need a shared picture of the target customer to align design and prioritization decisions. This Skill produces a structured proto-persona that makes assumptions explicit instead of designing for a vague generic user. ## Core Features & Use Cases - Structured persona template: Captures name, bio, quotes, pains, goals, and decision-making influences in a consistent markdown format. - Assumption tagging: Marks unvalidated claims with [ASSUMPTION—VALIDATE] so teams know what to research next. - Quality guardrails: Built-in pitfalls and quality checks prevent demographic-only personas, fabricated quotes, and persona sprawl. - Use Case: A product manager kicking off a new feature uses this Skill to synthesize sales call notes and support tickets into a "Manager Mike" proto-persona, then shares it with design to align on the target user before scheduling validation interviews. ## Quick Start Create a proto-persona for our target user based on our current research notes and market data, saving it to docs/product/.

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 without user research?▼

Synthesize available sources like sales calls, support tickets, analytics, and market reports into a structured profile covering bio, quotes, pains, and goals. Tag uncertain claims with [ASSUMPTION—VALIDATE] and plan interviews to test them.

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

A proto-persona is built in hours from assumptions and limited data, while a validated persona takes weeks of user research. Proto-personas align teams early and evolve rapidly; validated personas guide detailed design with high confidence.

When should I not use a proto-persona?▼

Skip proto-personas when you already have extensive user research or a mature product with known segments—in those cases build a validated persona instead. They are also not a substitute for quantitative data.

How many proto-personas should a team create?▼

Start with one or two proto-personas, typically a primary and secondary user. Creating many upfront causes analysis paralysis and prevents the team from focusing on a clear target user.

Why do proto-personas fail in practice?▼

Common failures include demographics without behavioral context, fabricated marketing-style quotes, treating assumptions as facts, and never validating the persona. Fix these by using real quotes, tagging assumptions, and running research sprints.