pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
What this skill does
# Strategies: Product-Market Fit Guides product-market fit (PMF) validation and measurement. PMF occurs when a product precisely meets market needs, creating widespread demand. ~99% of startups fail primarily due to PMF issues (vitamin problems, premature scaling). Use this skill when validating before scaling, measuring PMF, or diagnosing traction problems. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Definition **Product-market fit** (Marc Andreessen): "Being in a good market with a product that can satisfy that market." **Signals**: Customers buying rapidly; usage growing; word-of-mouth spreading organically; high retention, low churn. ## Sean Ellis 40% Test **Question**: "How would you feel if you could no longer use [product]?" | Response | Meaning | |----------|---------| | **Very disappointed** | Strong PMF signal | | Somewhat disappointed | — | | Not disappointed | — | | N/A – I no longer use | — | **Threshold**: 40%+ answering "very disappointed" = PMF achieved. Below 40% = iterate. | Score | Action | |-------|--------| | **Below 25%** | Significant changes needed | | **25–39%** | Close to PMF; iterate and improve | | **40%+** | PMF achieved | **Best practice**: Survey 40–50 active users (used product 2+ times in last 14 days). Segment by user type—some segments may have PMF while others don't. **Limitation**: Combine with retention curves, engagement, organic growth; avoid false positives in early stages. ## Vitamin vs Painkiller | Type | Definition | Adoption | |------|-------------|----------| | **Painkiller** | Solves urgent, acute problems; users actively seek solutions | Fast adoption; high retention; willing to pay | | **Vitamin** | Nice-to-have; incremental benefit; users can live without | Slow adoption; expensive marketing to succeed | **~99% of failures**: Solving vitamin problems instead of real pain. Validate: Would users be genuinely inconvenienced if your product vanished? **Validation**: Talk to users; listen for frustration; run pre-sells; check frequency and time-sensitivity of the problem. ## Key Indicators | Indicator | Strong PMF | |-----------|------------| | **Retention** | High; low churn | | **CAC vs CLTV** | CAC decreasing relative to CLTV | | **Activation** | Strong conversion to paying customers | | **Growth** | Organic; word-of-mouth | | **NPS** | High; enthusiastic advocacy | ## Common Failures | Failure | Avoid | |--------|-------| | **Vitamin problems** | Solve urgent pain, not nice-to-have | | **Vanity feedback** | Use retention data, not polite opinions | | **Premature scaling** | Validate PMF before scaling acquisition | | **Misalignment** | Customer-problem fit before product-build | ## Product Research & SaaS Context | Area | Notes | |------|-------| | **Product positioning** | Target audience; core value; competitive differentiation | | **Market research** | Competitor analysis; surveys; interviews to validate assumptions | | **SaaS form** | Cloud delivery; subscription; ease of use; dependency on industry standardization | | **Enterprise / ACV** | Customization; data security/private deployment; procurement cycles; buy vs SaaS trade-offs | **Use**: When discussing PMF for SaaS or enterprise—factor in product research rigor and ACV-specific challenges. See **gtm-strategy** for enterprise GTM. ## PMF as Continuous Process PMF is increasingly a **continuous validation**—markets evolve; re-measure as you expand. Target "PMF for a niche" first (40%+ in one segment) before broadening. ## Output Format - **PMF assessment** (current signals, Sean Ellis score if available) - **Vitamin vs Painkiller** diagnosis - **Validation** approach (interviews, pre-sells, metrics) - **Next steps** (iterate vs scale) ## Related Skills - **cold-start-strategy**: First users; avoid large-scale paid before PMF - **indie-hacker-strategy**: Indie hacker PMF; monetize day one; Ramen profitability - **paid-ads-strategy**: PMF testing (small budget) vs conversion-driven (post-PMF) - **google-ads**: PMF testing with landing page + $47–500 - **gtm-strategy**: GTM framework; PMF validation before scaling GTM - **product-launch**: Launch execution; validate PMF before scaling - **retention-strategy**: Retention as PMF signal; churn as anti-signal
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.