discovery

# Product Discovery

Transform product ideas into well-defined Product Requirements Documents (PRDs) through structured collaborative dialogue.

## Overview

Guide users through 5 phases to produce a complete PRD:
1. **Gate Check** - Determine scope and template
2. **Understanding** - Clarify the problem and context
3. **Exploring** - Evaluate approaches and trade-offs
4. **Design** - Define features, constraints, success criteria
5. **Capture** - Save the PRD document
6. **Transition** - Hand off to implementation

For detailed phase guidance, see `references/phase-guide.md`.

## Phase 1: Gate Check

Determine if discovery is needed and select the appropriate template.

**If requirements are already clear** (user provided detailed spec):
- Acknowledge the clarity
- Offer to refine or proceed directly to capture
- Ask if user wants full discovery anyway

**Template Selection** - Ask early:
> "Is this a quick feature enhancement or a significant initiative?"

| Response | Template | Use When |
|----------|----------|----------|
| Quick/small | `templates/prd-lite.md` | Bug fixes, minor enhancements, simple features |
| Significant | `templates/prd-full.md` | New features, architectural changes, multi-team work |

**Save Location** - Ask early:
> "Where should the PRD be saved? Check your CLAUDE.md for default location, or specify a path."

If user's CLAUDE.md has PRD save instructions, follow those. Otherwise, ask for explicit path.

## Phase 2: Understanding

Examine available context:
- User's initial idea or description
- Any existing documents mentioned
- Project or product context

Ask clarifying questions to build understanding:
- **One question at a time** - never overwhelm with multiple questions
- **Prefer multiple-choice** when natural options exist (use AskUserQuestion tool)
- **Open-ended is fine** when options aren't obvious

Focus questions on:
- Problem being solved and why it matters
- Target users and their context
- Key constraints (time, technology