Product Discovery

Conduct structured product discovery interviews to define intent, user segments, and pain points.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill product-discovery-carson-sweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Product Discovery
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/product-discovery
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill product-discovery-carson-sweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity of early-stage product development by guiding you through a structured interview process to define your product's intent, target audience, and market viability.

Core Features & Use Cases

  • Structured Discovery Levels: Choose between L1 (Intent/Boundaries), L2 (Problem/Success), or L3 (Full Pain Thesis) based on your project's maturity.
  • Compliance Mapping: Automatically identifies necessary regulatory frameworks like GDPR, HIPAA, or PCI-DSS based on your data and user geography.
  • Evidence-Based Validation: Generates a validation rubric to help you move from assumptions to quantified market evidence.

Quick Start

Initiate the product discovery process by running the product-discovery skill to begin the guided interview for your new project.

Frequently Asked Questions about Product Discovery

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

FAQPage Schema
How do I structure product discovery to validate market viability before development?

Product discovery structures early-stage validation by guiding you through a defined interview to outline project intent, target audience, and market pain points. This generates a comprehensive project discovery log to ensure strategic alignment.

What levels of product discovery can I use for an early-stage project?

Structured discovery levels include L1 for Intent and Boundaries, L2 for Problem and Success metrics, and L3 for a Full Pain Thesis. These levels scale based on your project's current maturity and research depth.

How do I map compliance frameworks like GDPR and HIPAA during user research?

Compliance mapping automatically identifies necessary regulatory frameworks like GDPR, HIPAA, or PCI-DSS based on collected user data and geography. This ensures product strategy aligns with legal requirements from the start.

Can I use structured product discovery for internal tools and hobby projects?

Yes, structured product discovery applies to the initial lifecycle phase of commercial products, internal tools, and hobby projects. It requires session state management to map assumptions into quantified market evidence.

What is the best way to move from product assumptions to quantified market evidence?

The best way to move from assumptions to quantified market evidence is by generating a validation rubric. This evidence-based validation mechanism helps define market viability within your project discovery log.

When should I not use a full pain thesis for product strategy?

Avoid using a full pain thesis if your project maturity only requires defining basic Intent and Boundaries or Problem and Success metrics. Selecting L1 or L2 discovery levels prevents unnecessary research overhead for early-stage concepts.