---

name: yepai-pm-proto-persona description: >- Use when the user needs an early-stage persona draft, practical target-user sketch, or sharper audience understanding for discovery, positioning, or product definition. Best for lightweight persona work before full research is available. metadata: {"openclaw":{"emoji":"🧑‍💼"}} license: MIT-0

YepAI PM Proto Persona

Use this skill when the team needs a practical working model of the target user.

Use Cases

• early discovery work
• new segment exploration
• positioning preparation
• PRD context building
• onboarding or workflow design
• "who exactly are we building for?"

Core Rule

A proto-persona is a working hypothesis, not a fictional biography. Prioritize operating context, pains, goals, and decision behavior over decorative demographics.

Proto-Persona Workflow

1. Define the user frame

Clarify:

• target segment
• role or job title
• environment or company context
• workflow they are trying to improve
• key constraints around them

2. Identify the operating reality

Look for:

• what they are responsible for
• what pressures they face
• what tools or workarounds they currently use
• what success looks like in their role

3. Capture pains, goals, and triggers

State:

• recurring pain points
• desired outcomes
• moments that trigger buying or switching behavior
• adoption blockers or anxieties

4. Map influence and decision behavior

Clarify:

• who influences their decisions
• whether they are a buyer, user, or champion
• what makes them trust a new solution

5. Keep uncertainty visible

Mark assumptions explicitly and end with validation suggestions.

Output Format

Prefer this structure:

## Persona Name
## Role / Context
## Core Responsibilities
## Current Workflow
## Main Pains
## Goals / Success Criteria
## Buying or Adoption Triggers
## Decision Influence
## Assumptions / Unknowns
## Recommended Next Step

Quality Rules

• Optimize for usefulness, not storytelling
• Avoid unsupported demographic filler
• Tie the persona to a workflow and problem
• Distinguish user, buyer, and champion when relevant
• Keep assumptions explicit