メニュー
Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill proto-personaコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
SOC 職業分類に基づく
SKILL.md を表示中
| name | proto-persona |
| argument-hint | [target user or segment] |
| description | Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation. |
| intent | Create an initial, assumption-based persona profile that synthesizes available user research, market data, and stakeholder knowledge into a working hypothesis about your target user. Use this to align teams early in product development, guide initial design decisions, and identify gaps in understanding that require validation through research. |
| type | component |
| theme | discovery-research |
| best_for | ["Getting a working customer profile before you can afford real research","Making team assumptions about users explicit and challengeable","Setting up a persona you intend to validate, not defend"] |
| scenarios | ["We have no research budget yet but need a working customer profile to start","Everyone on the team pictures a different user and it's causing arguments"] |
| estimated_time | 15-25 min |
Create an initial, assumption-based persona profile that synthesizes available user research, market data, and stakeholder knowledge into a working hypothesis about your target user. Use this to align teams early in product development, guide initial design decisions, and identify gaps in understanding that require validation through research.
This is not a validated persona—it's a "proto" (prototype) persona that evolves as you learn more. Think of it as a structured placeholder that prevents design-by-committee while acknowledging you don't have all the answers yet.
Works best with: The target user or segment you need a working profile for. Also useful: Whatever signal exists — support themes, sales anecdotes, analytics, prior research — plus the decision the persona will guide.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill asks who you think the user is and what you already know, then structures it and flags the assumptions needing validation.
Example invocation: Proto-persona for solo bookkeepers adopting our receipt-scanning app — signal: 30 support tickets and 4 sales call notes.
A proto-persona is a lightweight, hypothesis-driven persona created from:
| Proto-Persona | Validated Persona |
|---|---|
| Created in hours/days | Created over weeks/months |
| Based on assumptions + limited research | Based on extensive user research |
| Used to align teams early | Used to guide detailed design |
| Evolves rapidly | Stable over time |
| Good enough to start | High confidence |
Use template.md for the full fill-in structure.
Before creating a proto-persona, collect:
skills/problem-statement/SKILL.md)If missing context: Don't fabricate—note gaps and plan research to fill them.
Give the persona an alliterative, memorable name (makes it easier to reference).
### Name
- [Alliterative name, e.g., "Manager Mike," "Startup Sarah," "Enterprise Emma"]
Quality checks:
Describe who this person is in the real world.
### Bio & Demographics
- [Age range]
- [Geographic location]
- [Social status (married, single, family, etc.)]
- [Online presence (active on LinkedIn, avoids social media, etc.)]
- [Leisure activities]
- [Career status (job title, industry, seniority)]
Quality checks:
Example:
Use real or representative quotes that reveal how they think and speak.
### Quotes
- "[Quote 1 revealing what they say, feel, or think]"
- "[Quote 2 revealing frustrations or motivations]"
- "[Quote 3 revealing attitudes or beliefs]"
Quality checks:
Example:
What problems or frustrations does this persona experience? (Reference skills/jobs-to-be-done/SKILL.md for structure.)
### Pains
- [Pain point 1 related to the problem space]
- [Pain point 2 related to the problem space]
- [Pain point 3 related to the problem space]
Quality checks:
What behaviors, actions, or outcomes are they pursuing?
### What is This Person Trying to Accomplish?
- [Behavior or outcome 1]
- [Behavior or outcome 2]
- [Behavior or outcome 3]
Quality checks:
What are their wants, needs, dreams?
### Goals
- [Goal 1: want, need, or dream]
- [Goal 2: want, need, or dream]
- [Goal 3: want, need, or dream]
Quality checks:
Do they have the power to buy your solution?
### Attitudes & Influences
- **Decision-Making Authority:** [Yes/No + context (e.g., "Has budget authority up to $10k, needs exec approval above that")]
Quality checks:
Who influences their decisions?
- **Decision Influencers:** [Who influences this person? (e.g., "Boss, peers in industry Slack channels, analyst reports")]
Quality checks:
What beliefs and attitudes shape their decisions?
- **Beliefs & Attitudes:** [Beliefs/attitudes that impact decisions (e.g., "Skeptical of tools that require training," "Values data-driven decision making")]
Quality checks:
See examples/sample.md for full proto-persona examples.
Mini example excerpt:
### Name
- Manager Mike
### Quotes
- "I spend more time in status meetings than actually building product."
Symptom: "28 years old, lives in NYC, has a dog"
Consequence: Demographics don't explain why someone would use your product.
Fix: Add behavioral context: "Works remotely, active in 5 Slack communities, values async communication tools."
Symptom: "Manager Mike would never use feature X because he hates complexity"
Consequence: You're treating an assumption as validated research.
Fix: Add "[ASSUMPTION—VALIDATE]" tags and plan interviews to test hypotheses.
Symptom: Trying to model every possible user type upfront
Consequence: Analysis paralysis. Teams can't focus on a primary user.
Fix: Start with 1-2 proto-personas (primary + secondary). Add more as you validate and expand.
Symptom: Quotes that sound like marketing copy: "I love products that delight me!"
Consequence: Fake personas lead to fake empathy.
Fix: Use real quotes from interviews, support tickets, or sales calls. If you don't have quotes yet, note "[PLACEHOLDER—NEEDS RESEARCH]."
Symptom: Proto-persona created 6 months ago, never updated
Consequence: You're designing for a hypothesis that may be wrong.
Fix: Plan research sprints to validate key assumptions. Evolve the proto-persona as you learn. Graduate it to a validated persona when confidence is high.
skills/problem-statement/SKILL.md — Persona informs the "I am" sectionskills/jobs-to-be-done/SKILL.md — JTBD informs persona pains/goalsskills/positioning-statement/SKILL.md — Persona is the "For [target]"skills/user-story/SKILL.md — Stories use "As a [persona]"prompts/proto-persona-profile.md in the https://github.com/deanpeters/product-manager-prompts repo.Skill type: Component
Suggested filename: proto-persona.md
Suggested placement: /skills/components/
Dependencies: References skills/jobs-to-be-done/SKILL.md, skills/problem-statement/SKILL.md
Used by: skills/positioning-statement/SKILL.md, skills/user-story/SKILL.md, skills/problem-statement/SKILL.md