persona-development

Name: persona-development
Author: Productfculty-aipm

70stars33forks

How to install persona-development?

productfculty-aipm/pm-copilot-by-product-faculty/persona-development

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill persona-development

Installs into the current project.

Summary

Use this skill when the user asks to "create user personas", "develop personas", "write a persona", "define our users", "user profile", "who is our user", "help me define the target user", "create a user archetype", or wants to build or update structured user persona definitions

Files · 1

View on GitHub

SKILL.md

1	# Persona Development
2
3	You are building user personas grounded in real user behavior and JTBD thinking — not demographic templates. A persona is useful only if it changes what you build or how you communicate. If a persona doesn't make a decision obvious, it's not sharp enough.
4
5	Frameworks: Bob Moesta / JTBD (demand-side thinking), Hilary Gridley (AI-embracer vs. skeptic segmentation), Lean Startup (build-measure-learn).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for product context and any existing persona notes. Read `context/product/personas.md` if it exists — understand what's already there and whether it needs updating or creating from scratch.
10
11	If research data exists (interview notes, support tickets, survey responses), use it. If not, build a research-grounded hypothesis persona that can be validated.
12
13	## Step 2 — Persona Foundation
14
15	A good persona answers these questions from the user's perspective:
16
17	Who are they? (Role, situation, context — not demographics)
18	What are they trying to do? (The JTBD — what progress are they making?)
19	What's stopping them? (Pain, friction, workaround)
20	What does success look like for them? (Desired outcome — functional, emotional, social)
21	How do they currently handle this? (Current hire — the status quo)
22	What would make them switch? (Switch trigger)
23	How do they feel about AI assistance? (Embracer, neutral, or skeptic)
24
25	## Step 3 — JTBD-Grounded Persona
26
27	Write each persona with a demand-side framing:
28
29	Triggering situation: "When [specific situation arises], this persona needs to [make progress]."
30
31	This is more actionable than "They are 32 years old and work at a startup." The triggering situation tells you when the persona needs the product, not just who they are.
32
33	## Step 4 — AI Embracer vs. Skeptic Segmentation
34
35	Based on Hilary Gridley's segmentation: "The most meaningful segmentation for AI products is attitudinal: AI embracers vs. AI skeptics."
36
37	For each persona, identify their position:
38
39	AI Embracer:
40	- Excited about AI assistance; self-directed; tolerates setup friction
41	- Onboarding: jump straight to advanced features; show full capability surface
42	- Messaging: "What would you build if you had a senior PM teammate?"
43
44	AI Skeptic / Cautious:
45	- Trusts proven frameworks; fears losing craft or voice; needs to see before committing
46	- Onboarding: lead with framework credibility; show sample outputs first; emphasize they stay in control
47	- Messaging: "PM Copilot uses Teresa Torres and Marty Cagan's frameworks — not guesswork."
48
49	AI Neutral:
50	- Pragmatic; will use AI if it saves time; skeptical of hype
51	- Onboarding: show a concrete before/after; quantify time saved
52	- Messaging: "Run /write-prd and get a complete PRD in 10 minutes."
53
54	## Step 5 — Persona Template
55
56	For each persona, fill in:
57
58	Name: [Descriptive label — e.g. "The Founding PM" not "Sarah"]
59	Triggering situation: [When they need this product]
60	JTBD: [What progress they're trying to make — functional, emotional, social]
61	Current hire: [What they use today; what's wrong with it]
62	Switch trigger: [What would make them look for something different]
63	Pains: [3 specific frustrations with the current solution]
64	Gains: [3 specific outcomes a new solution would enable]
65	AI stance: [Embracer / Neutral / Skeptic]
66	Onboarding path: [How to onboard this persona given their AI stance]
67	Representative quote: [A real or composite quote that captures their core frustration]
68	What makes them a bad fit: [Who this product isn't for — prevents over-targeting]
69
70	## Step 6 — Anti-Persona
71
72	Write one anti-persona: the user who looks like a fit but isn't. This prevents wasted sales and support effort, and helps the team say no to feature requests from this segment.
73
74	## Step 7 — Output
75
76	Produce:
77	- 2–3 personas (primary, secondary, and anti-persona)
78	- Each persona filled in using the template above
79	- A 1-page "user cheat sheet" that captures the essential differences between the personas for team use
80
81	Offer to save to `context/product/personas.md` and update `memory/user-profile.md` with any new persona insights.

People who liked this also viewed

6 picks

Type

persona-development

70stars33forks

View on GitHub

How to install persona-development?

productfculty-aipm/pm-copilot-by-product-faculty/persona-development

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill persona-development

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Persona Development
2
3	You are building user personas grounded in real user behavior and JTBD thinking — not demographic templates. A persona is useful only if it changes what you build or how you communicate. If a persona doesn't make a decision obvious, it's not sharp enough.
4
5	Frameworks: Bob Moesta / JTBD (demand-side thinking), Hilary Gridley (AI-embracer vs. skeptic segmentation), Lean Startup (build-measure-learn).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for product context and any existing persona notes. Read `context/product/personas.md` if it exists — understand what's already there and whether it needs updating or creating from scratch.
10
11	If research data exists (interview notes, support tickets, survey responses), use it. If not, build a research-grounded hypothesis persona that can be validated.
12
13	## Step 2 — Persona Foundation
14
15	A good persona answers these questions from the user's perspective:
16
17	Who are they? (Role, situation, context — not demographics)
18	What are they trying to do? (The JTBD — what progress are they making?)
19	What's stopping them? (Pain, friction, workaround)
20	What does success look like for them? (Desired outcome — functional, emotional, social)
21	How do they currently handle this? (Current hire — the status quo)
22	What would make them switch? (Switch trigger)
23	How do they feel about AI assistance? (Embracer, neutral, or skeptic)
24
25	## Step 3 — JTBD-Grounded Persona
26
27	Write each persona with a demand-side framing:
28
29	Triggering situation: "When [specific situation arises], this persona needs to [make progress]."
30
31	This is more actionable than "They are 32 years old and work at a startup." The triggering situation tells you when the persona needs the product, not just who they are.
32
33	## Step 4 — AI Embracer vs. Skeptic Segmentation
34
35	Based on Hilary Gridley's segmentation: "The most meaningful segmentation for AI products is attitudinal: AI embracers vs. AI skeptics."
36
37	For each persona, identify their position:
38
39	AI Embracer:
40	- Excited about AI assistance; self-directed; tolerates setup friction
41	- Onboarding: jump straight to advanced features; show full capability surface
42	- Messaging: "What would you build if you had a senior PM teammate?"
43
44	AI Skeptic / Cautious:
45	- Trusts proven frameworks; fears losing craft or voice; needs to see before committing
46	- Onboarding: lead with framework credibility; show sample outputs first; emphasize they stay in control
47	- Messaging: "PM Copilot uses Teresa Torres and Marty Cagan's frameworks — not guesswork."
48
49	AI Neutral:
50	- Pragmatic; will use AI if it saves time; skeptical of hype
51	- Onboarding: show a concrete before/after; quantify time saved
52	- Messaging: "Run /write-prd and get a complete PRD in 10 minutes."
53
54	## Step 5 — Persona Template
55
56	For each persona, fill in:
57
58	Name: [Descriptive label — e.g. "The Founding PM" not "Sarah"]
59	Triggering situation: [When they need this product]
60	JTBD: [What progress they're trying to make — functional, emotional, social]
61	Current hire: [What they use today; what's wrong with it]
62	Switch trigger: [What would make them look for something different]
63	Pains: [3 specific frustrations with the current solution]
64	Gains: [3 specific outcomes a new solution would enable]
65	AI stance: [Embracer / Neutral / Skeptic]
66	Onboarding path: [How to onboard this persona given their AI stance]
67	Representative quote: [A real or composite quote that captures their core frustration]
68	What makes them a bad fit: [Who this product isn't for — prevents over-targeting]
69
70	## Step 6 — Anti-Persona
71
72	Write one anti-persona: the user who looks like a fit but isn't. This prevents wasted sales and support effort, and helps the team say no to feature requests from this segment.
73
74	## Step 7 — Output
75
76	Produce:
77	- 2–3 personas (primary, secondary, and anti-persona)
78	- Each persona filled in using the template above
79	- A 1-page "user cheat sheet" that captures the essential differences between the personas for team use
80
81	Offer to save to `context/product/personas.md` and update `memory/user-profile.md` with any new persona insights.

People who liked this also viewed

6 picks

Type