discover

Transform vague product ideas into evidence-based problem statements for PRD creation.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill discover-jnlanahan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/1-Discover
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill discover-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you stop guessing when your idea is vague by surfacing a specific, evidence-backed problem statement that’s ready to hand off to PRD work.

Core Features & Use Cases

  • Step-based discovery across sessions: frames the problem space, identifies a specific customer, sharpens the problem, defines stakes, and synthesizes into a PRD-ready summary.
  • Persistent state management: tracks progress in .claude/discovery-notes.md so you can pause and resume without losing context.
  • Fast handoff to /prd: at completion (or when you choose to skip), it produces structured notes that /prd can consume to avoid redundant interviews.

Quick Start

Run /discover and answer the step-by-step prompts until you reach the PRD-ready summary.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I turn a vague product idea into a PRD-ready problem statement?

Product discovery transforms a vague idea into a PRD-ready problem statement by decomposing it into frame, customer, problem, stakes, and bridge steps, surfacing evidence-backed context for what to build.

How does multi-session product discovery work with persistent state tracking?

Multi-session product discovery tracks progress in `.claude/discovery-notes.md`, allowing you to pause and resume problem framing across customer, context, and urgency dimensions without losing context.

What is problem framing in product discovery and when do I need it?

Problem framing in product discovery is the process of sharpening an unvalidated idea into a specific customer problem. You need it when you do not yet know what to build and must gather evidence before PRD creation.

Can I hand off discovery notes directly to PRD creation without redundant interviews?

Yes, at completion the discovery process produces structured notes for a fast handoff to `/prd`, which consumes the evidence-based problem summary to skip further front-door interviewing.

What are the limitations of using step-based discovery for customer research?

Step-based discovery requires completing the frame, customer, problem, stakes, and bridge decomposition steps to produce a valid summary, meaning partial execution yields incomplete problem framing outputs.

Do I need any dependencies or components to run product discovery?

No dependencies or components are required to run product discovery. You only need to execute the command and answer the step-by-step prompts to generate the PRD-ready notes.