proto-persona

Create assumption-based customer persona hypotheses from research and stakeholder knowledge.

358|11|Updated May 15, 2026
One-click install
npx skills add https://github.com/getcrew44/crew44 --skill proto-persona-getcrew44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proto-persona
Source: https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/product/proto-persona
Command: npx skills add https://github.com/getcrew44/crew44 --skill proto-persona-getcrew44

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

proto-persona helps you quickly create an assumption-based customer profile from available research and signals, so teams can align early without waiting for extensive validation.

Core Features & Use Cases

  • Hypothesis-driven persona creation: Synthesizes user research, market data, and stakeholder knowledge into a structured proto persona.
  • Alignment and gap discovery: Clarifies what is known versus unknown, and surfaces specific research gaps to validate assumptions.
  • Shared artifact across product work: Produces a reusable persona draft that supports early design decisions, positioning, and user-story writing.

Quick Start

Use proto-persona to draft a persona for your current feature by providing the available research, market context, and stakeholder insights, then mark any uncertain points as assumptions to validate later.

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 discovery?

A proto persona is an assumption-based customer profile synthesizing existing market signals and stakeholder knowledge. You need one during early product development or pivots to establish a shared target user reference before committing to extensive validation research.

How do I create a persona hypothesis from limited user research?

Create a persona hypothesis by structuring available identity traits, quotes, pains, goals, and decision factors from current context. Synthesize stakeholder knowledge and market data without fabricating unknown facts, explicitly labeling gaps for follow-up research.

Can I use a proto persona to align my team before user validation?

Yes, you can use a proto persona to align teams before user validation. It clarifies known versus unknown user attributes, allowing early design decisions and user-story writing to proceed while surfacing specific research gaps to test later.

Does building a proto persona require completed customer research?

Building a proto persona does not require completed customer research. It synthesizes current market signals and stakeholder insights into a working hypothesis, explicitly marking uncertain points as assumptions to validate through future research.

What is the best way to document assumptions in a proto persona?

The best way to document assumptions in a proto persona is to explicitly label gaps in user identity, pains, and goals. Mark uncertain points as assumptions to validate later, ensuring the artifact remains a transparent hypothesis rather than fabricated fact.

When should I avoid using a proto persona for feature kickoffs?

You should avoid using a proto persona as a permanent user model for feature kickoffs. It is an early alignment tool for surfacing research gaps, meaning it should not replace direct customer validation or obscure unknown facts with fabricated details.