スキル一覧に戻る
majesticlabs-dev

pmf-validation

by majesticlabs-dev

18🍴 1📅 2026年1月24日
GitHubで見るManusで実行

SKILL.md


name: pmf-validation description: Validate product-market fit through assumption testing, customer discovery, and MVP strategy.

PMF Validation

Frameworks for achieving and measuring product-market fit.

  • pm-assumption-mapping - Prioritizing assumptions by risk
  • pm-customer-interviews - Discovery interview techniques
  • pm-jobs-to-be-done - Understanding customer motivations

Assumption Risk Framework

High Risk (Validate First)

AssumptionValidation MethodSuccess Criteria
Problem existsCustomer interviews (10+)7/10 confirm problem
Willing to payPrice testing, pre-orders3+ paying commitments
Pain is acuteSeverity scoringAverage 8+/10

Medium Risk (Validate During MVP)

AssumptionValidation MethodSuccess Criteria
Features priorityUsage analytics60%+ use core feature
Channel worksA/B testingCAC < 1/3 LTV
PositioningCompetitive testingClear preference signals

Low Risk (Validate Post-Launch)

  • Scale assumptions
  • Expansion opportunities
  • Adjacent markets

MVP Strategy

Definition Criteria

ElementQuestionOutput
Core valueWhat's the one thing it MUST do?Single feature
Target userWho has this problem most acutely?Narrow persona
Success metricHow do we know it works?Measurable KPI
TimelineWhat's the fastest we can test?Weeks, not months

Feature Prioritization

CategoryInclude in MVPDefer
Must-haveCore value deliveryEnhancement features
DifferentiatorKey unique angleSecondary differentiators
Table stakesMinimum viableNice-to-haves

Validation Methodology

Customer Discovery Script

Opening (2 min)

  • Build rapport
  • Explain purpose: learning, not selling

Problem Exploration (10 min)

  • "Tell me about the last time you dealt with [problem]..."
  • "What did you try? What worked/didn't work?"
  • "On a scale of 1-10, how painful is this?"

Solution Testing (5 min)

  • "If you could wave a magic wand, what would happen?"
  • "I'm working on something that [brief description]..."
  • "Would this help? Why or why not?"

Commitment Testing (3 min)

  • "Would you be interested in trying an early version?"
  • "What would you expect to pay for something like this?"
  • "Can I follow up when we have something to show?"

Signal Interpretation

SignalMeaningAction
"I'd pay for this"InterestGet specific on price
"Keep me updated"LukewarmFind stronger pain
"I already have X"CompetitionDifferentiate or pivot
"Let me introduce you to..."EnthusiasmStrong signal

Decision Framework

Green Light (Proceed)

  • 70%+ confirm problem exists
  • 3+ paying commitments
  • Clear differentiation
  • Unit economics work

Yellow Light (Iterate)

  • Mixed feedback on value prop
  • Price resistance but interest
  • Unclear positioning
  • Channel uncertainty

Red Light (Pivot)

  • <30% problem confirmation
  • No willingness to pay
  • Existing solutions "good enough"
  • No user enthusiasm

PMF Indicators

MetricPre-PMFAt PMFStrong PMF
Retention<20%40%+60%+
NPS<2040+60+
Word of mouth<10%25%+40%+
Revenue growthFlat20%+ MoM50%+ MoM
Inbound demandNoneSomePull > Push

スコア

総合スコア

60/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です