product-discovery

name	product-discovery
description	Conducts discovery sessions for features/products. Explores concept definition, business model, user journeys, competitive analysis, scoping decisions, and data modeling. Use when you need to explore "what is X", "let's understand", "discovery for", or the /discovery command.

Discovery Skill

Conduct structured discovery sessions for features and products. This skill helps PMs explore and document a problem space before writing PRDs or creating user stories.

Triggers

Explicit command:

• /discovery [feature-name]

Auto-detection patterns:

• "what is [X]"
• "let's explore [X]"
• "discovery for [X]"
• "I want to understand [X]"
• "let's debate/discuss [X]"

---

Workflow Overview

The discovery process has 7 flexible phases. All phases are optional—ask the user which aspects they want to explore at the start.

Phase 1: Concept Definition   → What is it?
Phase 2: Business Model       → Who manages it, for whom, how is it monetized?
Phase 3: Journey Mapping      → How do personas interact?
Phase 4: Competitive Analysis → How do competitors solve this? (OPTIONAL)
Phase 5: Scoping Decisions    → What goes into v1 vs. later?
Phase 6: Data Model           → What entities and behaviors? (OPTIONAL)
Phase 7: Documentation        → Compile into a research document

---

Phase 1: Concept Definition

Objective: Establish a shared understanding of what the concept/feature is.

Approach: Open-ended questions first, then structuring.

Steps

1.1 Initial open-ended question
    └── "What do you understand by [X]?"
    └── "Tell me more about [X]"

1.2 Active listening + synthesis
    └── Rephrase what the user said
    └── "So [X] is [my interpretation]. Is that correct?"

1.3 Iterate until alignment
    └── As many questions as necessary
    └── Do not proceed with doubts

1.4 Concept checkpoint
    └── Summarize agreed definition
    └── "Before moving on, I confirm: [X] is [final definition]"