Agent skill · product strategy · daffy0208
Product Strategist
Validate product-market fit and strategic direction. Use when defining new products, validating problem-solution fit, prioritizing features, or making build-vs-buy decisions. Focuses on discovery and validation before development.
Why this skill is useful
Provides a structured framework for validating product-market fit that includes specific methodologies and decision rules not commonly found in generic resources.
What it needs
About 6k tokens when loaded. Last updated 2025-12-25. 33 stars on the source repository.
What this skill does
Product Strategist Validate that products solve real problems for viable markets before investing in development. Core Principle Evidence over intuition. Test the riskiest assumptions first, fail fast, and validate with real user behavior—not opinions. 5-Phase Validation Process Phase 1: Problem Validation Goal: Confirm the problem is frequent, painful, and urgent enough that users will pay to solve it Activities: Define problem hypothesis: What problem are you solving? Identify target customer segments Conduct customer discovery interviews (10-15 per segment) Quantify problem severity: time/money cost to users Document current workarounds and their pain points The "Mom Test" Questions: ✅ Good Questions (reveal behavior): "Tell me about the last time you encountered [problem]." "How are you currently solving this?" "How much time/money do you spend on this problem?" "What have you tried that didn't work?" ❌ Bad Questions (confirmation bias): "Would you use this product?" (Everyone says yes) "Do you think this is a good idea?" (Asks opinion, not behavior) "How much would you pay for this?" (Hypothetical) Problem Severity Matrix: Dimension Low (Don't Build) Medium (Validate More) High (Build It) ----------------------- ----------------- ---------------------- ----------------- Frequency Happens rarely Monthly Daily/Weekly Impact Minor annoyance Wastes 1-2 hours Critical blocker Urgency Can wait Should fix eventually Need it now Willingness to Pay Won't pay Might pay $5-20/mo Will pay $50+/mo Current Workarounds Works fine Tolerable Painful/expensive Decision Rule: 4-5 High → Build immediately 2-3 High → Validate solution 0-1 High → Don't build (problem not severe enough) Validation Gate: [ ] 10+ customer discovery interviews completed [ ] Problem validated as frequent, painful, and urgent [ ] Current workarounds documented and evaluated [ ] Willingness to pay signals collected [ ] 70%+ of interviewees confirm problem is severe --- Phase 2: Solution Validation Goal: Te …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daffy0208/product-strategist