pm-pmf-signal
Use when defining how you'll know product-market fit has been reached — PMF survey, retention target, go/no-go threshold — or when 10-customer-discovery.md exists but no PMF signal plan yet. Step 11, final, of the idea-to-mvp flow (Lean PMF search).
התקנת הסקיל
/plugin marketplace add oferregev81pt/ai-pm-skills/plugin install idea-to-mvp@ai-pm-skills
Step 11 — PMF Signal
Different question from step 7. 07-validation.md asks "did we build the
MVP right, and what would kill it before launch?" This step asks "once real
people are using it, how do we know we've found product-market fit?"
Prerequisites
Read 00-status.md, 06-mvp-scope.md, 07-validation.md, and
10-customer-discovery.md if its synthesis exists. Missing
07-validation.md → offer to run pm-validation first, or proceed with an
explicit Gap: no prior north-star metric note with the PM's consent.
Drafting instructions (dispatch to a subagent when available, else inline)
Draft:
- PMF survey plan — the Sean Ellis question ("how would you feel if you could no longer use <product>?" very disappointed / somewhat disappointed / not disappointed), who to send it to (active users only, minimum usage threshold), and the 40%-very-disappointed pass bar.
- Retention target — a cohort retention curve/number appropriate to the product category, reusing 07's north-star metric as the retained behavior wherever possible instead of inventing a second metric.
- Qualitative signals — organic referrals, inbound demand, usage outpacing marketing spend; drawn from 10's synthesis where it exists.