Loading...
Loading...
Found 34 Skills
Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions.
Define a Proof of Life (PoL) probe—a lightweight validation artifact that surfaces harsh truths before expensive development. Use it to test hypotheses with minimal investment.
Help users conduct effective usability testing. Use when someone is planning user tests, designing prototype validation, preparing usability studies, or trying to understand why users struggle with their product.
Turns ideas into working prototypes and MVPs with the smallest useful scope. Use when validating a core hypothesis, shipping a demo-ready flow, or choosing a practical stack for fast learning.
Design Sprint methodology based on Jake Knapp's "Sprint" (Google Ventures). Use when you need to: (1) validate product ideas in 5 days instead of months, (2) rapidly prototype and test solutions, (3) answer critical business questions quickly, (4) align teams on product direction, (5) de-risk product development before building, (6) test multiple concepts with real users, (7) make fast strategic decisions through structured process.
Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but don't buy", "leading questions", or "The Mom Test". Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.
Facilitates the second step of a proven customer-interview method: recording the user's current best guesses — hypotheses — as numbered, falsifiable statements (H1, H2, …), each mapped to the goal questions it addresses, so interviews can confirm or contradict them instead of confirmation bias quietly filtering what's heard. Takes a GOALS.md goal-question list as input (file or pasted), elicits what the user believes goal by goal, sharpens vague beliefs into testable claims, prunes to hypotheses whose resolution would actually change what the user builds, targets, charges, or says, and preserves the result in HYPOTHESES.md. Load when the user has goal questions and wants to write hypotheses, list their assumptions, or record predictions before interviewing customers — 'I have my goals, what's next,' 'help me write down what I believe about my customers.' Do NOT load for writing the interview questions themselves, for analyzing interviews already conducted, or for statistical hypothesis testing.
Use when asked to "run a design sprint", "5-day sprint", "prototype in a week", "test ideas before building", or "Jake Knapp sprint". Helps teams go from problem to tested prototype in five days. The Design Sprint framework (created by Jake Knapp at Google Ventures) compresses months of work into one focused week.
Use when validating product assumptions before building, discovering unmet user needs, understanding customer problems and workflows, testing concepts or positioning, researching target markets, identifying jobs-to-be-done and hiring triggers, uncovering pain points and workarounds, or when users mention user research, customer interviews, surveys, discovery interviews, validation studies, or voice of customer.
Use when the user wants to validate a product idea, find pain points, mine demand signals, discover objections, or gather voice-of-customer language from Reddit, social posts, video transcripts, and comments. Produces evidence-backed product research.
Run market research for a product or feature idea using Ivan Zamesin's AJTBD / Next Move Theory methodology (distinct from generic Christensen JTBD). Output — an A4 one-pager with a GO / NARROW / PIVOT verdict plus a detailed report — market sizing, customer segments scored on the selection screen, competitors defined by Jobs, a differentiation hypothesis, an action-first risk plan, and ranked strategic options including alternative markets to pivot into. Use whenever the user wants to size a market, find or evaluate segments and Jobs, assess competitors, decide whether an idea is worth pursuing, or explore a pivot — even if they don't say "market research". Two modes — Quick (default; fast; no internet) and Deep (subagents + web research). Writes in plain language with methodology terms in parentheses. Defaults to English; adapts to the user's language.
Plan, run, and synthesize usability tests and produce a Usability Test Pack (test plan, tasks/script, logistics, notes template, issue log, findings + recommendations). Use for usability test, user test, prototype test, user testing, usability study, Wizard of Oz, fake door.