proto-persona

Create assumption-based proto-personas from research, analytics, and stakeholder insights.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill proto-persona-sicktastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proto-persona
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/proto-persona
Command: npx skills add https://github.com/sicktastic/skill-issue --skill proto-persona-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured way to capture assumption-based insights about your target customer when you lack validated research, so teams can align quickly without waiting for long studies.

Core Features & Use Cases

  • Context synthesis: Guides you to gather research, analytics, market data, and stakeholder knowledge to inform the persona.
  • Template-driven creation: Includes a fillable template that walks through identity, quotes, pains, goals, and attitudes to keep the profile actionable.
  • Use case: Kick off a new feature or pivot by documenting a proto-persona that highlights current assumptions, surfacing gaps for future interviews.

Quick Start

Use the proto-persona template to capture available research, market signals, and stakeholder insights into a working customer profile before deeper validation.

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 should I use it in product development?

A proto-persona is an assumption-based customer profile synthesizing stakeholder insights and market signals. Use it during early stage product development, feature kickoffs, and alignment sessions when validated research is limited and you need to align teams quickly.

How do I create a proto-persona using stakeholder insights and market data?

To create a proto-persona, gather collected interviews, analytics, market data, and stakeholder insights to document customer identity, pains, goals, and influences using a structured template, surfacing current assumptions and gaps for future validation.

Can I build a user persona without conducting long user research studies?

Yes, you can build an assumption-based proto-persona without long studies by synthesizing available market signals, analytics, and team knowledge into a working customer profile, allowing teams to align quickly while documenting gaps for future research.

What is the best way to align teams on target customer assumptions before deep validation?

The best way to align teams is creating a proto-persona that highlights current assumptions using a template-driven approach, capturing identity, quotes, pains, and goals to document stakeholder knowledge before investing in deeper validation.

Do I need collected interviews and analytics to document a proto-persona?

Yes, creating a proto-persona requires collected interviews, analytics, market data, and stakeholder insights as inputs to document identity, pains, goals, and influences accurately, even though the resulting profile remains assumption-based.

Why does my proto-persona need to surface assumptions during feature kickoffs?

Your proto-persona needs to surface assumptions during feature kickoffs to highlight gaps in current understanding, guiding future interviews and ensuring stakeholder alignment on target customer identity, pains, and goals before committing resources.