product-discovery

Clarify customer problems and define testable MVP validation experiments.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahsanghalib/ai-workflow --skill product-discovery-ahsanghalib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/ahsanghalib/ai-workflow/tree/main/skills/product-discovery
Command: npx skills add https://github.com/ahsanghalib/ai-workflow --skill product-discovery-ahsanghalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often jump to solutions before validating the customer problem, wasting effort on features nobody needs. This Skill structures early-stage product discovery so decisions rest on classified evidence rather than assumptions. ## Core Features & Use Cases - Customer and Job Framing: Captures ICP, jobs-to-be-done, triggering events, workarounds, and cost of inaction before any solution discussion. - Evidence Ledger: Classifies every claim as observed behavior, user report, sourced fact, inference, assumption, or unknown, with confidence and contradicting evidence. - MVP and Validation Design: Defines the smallest testable promise, non-goals, falsifiable hypotheses, success thresholds, and kill criteria for each experiment. - Use Case: A founder believes small businesses need automated invoicing. Use this Skill to interview the evidence, rank risky assumptions, compare alternatives including doing nothing, and produce a discovery brief with a proposed validation experiment. ## Quick Start Ask the assistant to run product discovery on your product idea and produce a discovery brief covering the customer, evidence, assumptions, MVP scope, and validation experiments.

Frequently Asked Questions about product-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a product idea before building it?▼

Validate a product idea by framing the customer problem and job-to-be-done, classifying your evidence, ranking assumptions by risk, and defining the smallest testable promise. Each experiment needs a falsifiable hypothesis, success threshold, and kill criterion before execution.

How to define an MVP scope for a new product?▼

Define MVP scope as the smallest testable promise that targets your riskiest assumption, with explicit non-goals. The Skill produces a discovery brief listing the MVP, the assumption it tests, and the validation experiments with timeboxes and thresholds.

What is a jobs-to-be-done analysis for product discovery?▼

Jobs-to-be-done analysis captures the customer's context, triggering event, desired outcome, current workaround, and cost of inaction. It distinguishes the user, buyer, and beneficiary so demand is inferred from evidence rather than solution preference.

When should I not use a product discovery workflow?▼

Do not use product discovery for technical architecture, delivery planning, or founder-level decisions about capital and hiring. Those hand off to technical-design, project-init, and founder-decision workflows respectively.

Can product discovery run customer experiments automatically?▼

No. Experiments are proposals, not executions. The Skill requires explicit approval before contacting users, launching surveys, publishing material, or deploying prototypes, and it stops after delivering the discovery brief.