pmf-hypothesis-builder

Name: pmf-hypothesis-builder
Author: gnurio

2installs4forks

How to install pmf-hypothesis-builder?

gnurio/pmf-plugin/pmf-hypothesis-builder

$npx -y skills add gnurio/pmf-plugin --skill pmf-hypothesis-builder

Installs into the current project.

Summary

Guide user through defining initial PMF narrative with 6 dimensions, confidence scores, and validation priorities. This skill should be used when starting a new product-market fit discovery process or formalizing an initial product insight into a structured hypothesis.

Files · 1

View on GitHub

SKILL.md

1	# PMF Hypothesis Builder
2
3	This skill guides the user through creating a structured initial Product-Market Fit (PMF) narrative across 6 dimensions. It transforms an initial product insight into a comprehensive hypothesis ready for validation.
4
5	## Purpose
6
7	Create a Version 1 PMF Narrative document that:
8	1. Defines all 6 PMF dimensions with clarity and specificity
9	2. Assesses confidence levels for each dimension
10	3. Identifies the riskiest dimension(s) requiring validation
11	4. Establishes a baseline for iterative refinement through evidence gathering
12
13	## When to Use This Skill
14
15	Use this skill when:
16	- Starting a new product-market fit discovery process for a zero-to-one startup
17	- Formalizing a product idea within an established organization
18	- Creating a new product extension and need to validate PMF
19	- The user has an initial insight but hasn't structured it into the 6 PMF dimensions
20	- Restarting PMF discovery after a major pivot or reset
21
22	Do NOT use this skill when:
23	- The user already has a complete PMF narrative document (use `/pmf-status` instead)
24	- The user needs to validate an existing hypothesis (use `/pmf-market-research` instead)
25	- The user is measuring PMF for an existing product (use `/pmf-metrics-setup` instead)
26
27	## Workflow
28
29	### Phase 1: Setup and Context Gathering
30
31	1. Ask for project location preference:
32	Use AskUserQuestion to determine where to create the PMF project folder:
33
34	```
35	Question: "Where should the PMF project folder be created?"
36	Header: "Location"
37	Options:
38	1. "Obsidian vault (01 PROJECTS/pmf-{product-name}/) - Recommended"
39	Description: "Integrates with existing PARA system, searchable, synced via iCloud"
40	2. "Custom location (user specifies path)"
41	Description: "Standalone folder outside vault for cleaner separation"
42	```
43
44	2. Gather initial context:
45	Use AskUserQuestion to collect essential information before building the narrative:
46
47	```
48	Question 1: "What type of product are you building?"
49	Header: "Product Type"
50	Options:
51	- "B2C SaaS" / "B2B SaaS" / "Marketplace" / "DTC E-commerce" / "Other"
52
53	Question 2: "What is your organizational context?"
54	Header: "Org Context"
55	Options:
56	- "Zero-to-one startup (new company)"
57	- "New product in established organization"
58	- "Product extension/feature expansion"
59	```
60
61	If product type is B2B SaaS or Marketplace:
62	Use AskUserQuestion:
63	```
64	Question: "This product has multiple user roles. Should we define PMF dimensions separately for each role?"
65	Header: "Multi-Role"
66	Options:
67	- "Yes, define separately (Recommended)" - Creates richer, more accurate hypothesis
68	- "No, keep unified" - Simpler, but may miss role-specific nuances
69	```
70
71	If user selects "Yes":
72	- For B2B: "We'll consider Decision-Makers (who buy) vs End-Users (who use)"
73	- For Marketplace: "We'll consider Demand Side (buyers) vs Supply Side (sellers)"
74
75	Note: If multi-role approach is selected, guide user through dimensions for each role separately, then synthesize.
76
77	3. Create project folder structure:
78	```
79	{project-root}/pmf-{product-name}/
80	├── pmf-narrative.md # To be created in this skill
81	├── research/ # Empty, for future use
82	├── validation/ # Empty, for future use
83	├── interviews/ # Empty, for future use
84	└── measurement/ # Empty, for future use
85	```
86
87	### Phase 2: Interactive Narrative Building
88
89	Guide the user through defining each dimension in sequence. Use the `references/pmf-framework.md` file for detailed criteria and examples.
90
91	#### Step 1: Initial Insight Quality Check
92
93	Before defining dimensions, validate the initial insight meets quality criteria:
94
95	Use AskUserQuestion to assess:
96	```
97	Question: "Describe the insight that led to this product idea. How did you discover this opportunity?"
98	```
99
100	Then evaluate against criteria:
101	- Earned: From personal experience/observation (not brainstorming)
102	- Unique: Under-appreciated, not obvious
103	- Grounded: Aligns with at least 1 existing capability/strategy
104
105	If insight quality is weak, suggest analog research to strengthen it before proceeding.
106
107	#### Step 2: Define Problem to Solve
108
109	Display "What Good Looks Like": "Good problem definitions are broad, independent from solution, avoiding 'solution thinking'. Frame as problems, not solutions."
110
111	Guide user through the outcome-motivation gap framework:
112
113	1. Ask: "What are customers trying to achieve?" (desired outcome)
114	2. Ask: "Why do they want this?" (motivation)
115	3. Ask: "Why can't they do this?" (gap)
116
117	Critical validation: Ensure the problem is framed as a problem, NOT a solut

People who liked this also viewed

6 picks

Type

pmf-hypothesis-builder

2installs4forks

View on GitHub

How to install pmf-hypothesis-builder?

gnurio/pmf-plugin/pmf-hypothesis-builder

$npx -y skills add gnurio/pmf-plugin --skill pmf-hypothesis-builder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# PMF Hypothesis Builder
2
3	This skill guides the user through creating a structured initial Product-Market Fit (PMF) narrative across 6 dimensions. It transforms an initial product insight into a comprehensive hypothesis ready for validation.
4
5	## Purpose
6
7	Create a Version 1 PMF Narrative document that:
8	1. Defines all 6 PMF dimensions with clarity and specificity
9	2. Assesses confidence levels for each dimension
10	3. Identifies the riskiest dimension(s) requiring validation
11	4. Establishes a baseline for iterative refinement through evidence gathering
12
13	## When to Use This Skill
14
15	Use this skill when:
16	- Starting a new product-market fit discovery process for a zero-to-one startup
17	- Formalizing a product idea within an established organization
18	- Creating a new product extension and need to validate PMF
19	- The user has an initial insight but hasn't structured it into the 6 PMF dimensions
20	- Restarting PMF discovery after a major pivot or reset
21
22	Do NOT use this skill when:
23	- The user already has a complete PMF narrative document (use `/pmf-status` instead)
24	- The user needs to validate an existing hypothesis (use `/pmf-market-research` instead)
25	- The user is measuring PMF for an existing product (use `/pmf-metrics-setup` instead)
26
27	## Workflow
28
29	### Phase 1: Setup and Context Gathering
30
31	1. Ask for project location preference:
32	Use AskUserQuestion to determine where to create the PMF project folder:
33
34	```
35	Question: "Where should the PMF project folder be created?"
36	Header: "Location"
37	Options:
38	1. "Obsidian vault (01 PROJECTS/pmf-{product-name}/) - Recommended"
39	Description: "Integrates with existing PARA system, searchable, synced via iCloud"
40	2. "Custom location (user specifies path)"
41	Description: "Standalone folder outside vault for cleaner separation"
42	```
43
44	2. Gather initial context:
45	Use AskUserQuestion to collect essential information before building the narrative:
46
47	```
48	Question 1: "What type of product are you building?"
49	Header: "Product Type"
50	Options:
51	- "B2C SaaS" / "B2B SaaS" / "Marketplace" / "DTC E-commerce" / "Other"
52
53	Question 2: "What is your organizational context?"
54	Header: "Org Context"
55	Options:
56	- "Zero-to-one startup (new company)"
57	- "New product in established organization"
58	- "Product extension/feature expansion"
59	```
60
61	If product type is B2B SaaS or Marketplace:
62	Use AskUserQuestion:
63	```
64	Question: "This product has multiple user roles. Should we define PMF dimensions separately for each role?"
65	Header: "Multi-Role"
66	Options:
67	- "Yes, define separately (Recommended)" - Creates richer, more accurate hypothesis
68	- "No, keep unified" - Simpler, but may miss role-specific nuances
69	```
70
71	If user selects "Yes":
72	- For B2B: "We'll consider Decision-Makers (who buy) vs End-Users (who use)"
73	- For Marketplace: "We'll consider Demand Side (buyers) vs Supply Side (sellers)"
74
75	Note: If multi-role approach is selected, guide user through dimensions for each role separately, then synthesize.
76
77	3. Create project folder structure:
78	```
79	{project-root}/pmf-{product-name}/
80	├── pmf-narrative.md # To be created in this skill
81	├── research/ # Empty, for future use
82	├── validation/ # Empty, for future use
83	├── interviews/ # Empty, for future use
84	└── measurement/ # Empty, for future use
85	```
86
87	### Phase 2: Interactive Narrative Building
88
89	Guide the user through defining each dimension in sequence. Use the `references/pmf-framework.md` file for detailed criteria and examples.
90
91	#### Step 1: Initial Insight Quality Check
92
93	Before defining dimensions, validate the initial insight meets quality criteria:
94
95	Use AskUserQuestion to assess:
96	```
97	Question: "Describe the insight that led to this product idea. How did you discover this opportunity?"
98	```
99
100	Then evaluate against criteria:
101	- Earned: From personal experience/observation (not brainstorming)
102	- Unique: Under-appreciated, not obvious
103	- Grounded: Aligns with at least 1 existing capability/strategy
104
105	If insight quality is weak, suggest analog research to strengthen it before proceeding.
106
107	#### Step 2: Define Problem to Solve
108
109	Display "What Good Looks Like": "Good problem definitions are broad, independent from solution, avoiding 'solution thinking'. Frame as problems, not solutions."
110
111	Guide user through the outcome-motivation gap framework:
112
113	1. Ask: "What are customers trying to achieve?" (desired outcome)
114	2. Ask: "Why do they want this?" (motivation)
115	3. Ask: "Why can't they do this?" (gap)
116
117	Critical validation: Ensure the problem is framed as a problem, NOT a solut

People who liked this also viewed

6 picks

Type