prd-interview

# PRD Interview Skill

Guide comprehensive interviews to transform rough ideas into actionable Product Requirements Documents through structured discovery across 8 categories.

## Core Interview Process

### Interview Flow

1. **Initial Prompt**: Capture the base idea in user's own words
2. **Category-Based Discovery**: Work through relevant categories using AskUserQuestion
3. **Adaptive Branching**: Skip irrelevant questions based on context
4. **Progressive Summarization**: Summarize after each category before moving on
5. **Document Generation**: Create the final PRD with Mermaid diagrams
6. **Task Integration**: Offer to generate hierarchical tasks via taskmanager

### Interview Categories

Conduct interviews across these 8 categories (adapt based on PRD type):

| Category | Focus Areas | When to Use |
|----------|-------------|-------------|
| Problem & Context | Pain points, current state, why now | Always |
| Users & Customers | Personas, segments, user journeys | Always |
| Solution & Features | Feature list, MVP scope, priorities | Always |
| Technical Implementation | Architecture, stack, integrations | Always |
| Business & Value | ROI, pricing, revenue model | Products, major features |
| UX & Design | Flows, wireframes, accessibility | UI-facing work |
| Risks & Concerns | Dependencies, assumptions, blockers | Always |
| Testing & Quality | Test strategies, acceptance criteria | Always |

### Question Guidelines

When using AskUserQuestion:
- Ask 2-4 questions per round maximum
- Provide concrete options when possible
- Enable multiSelect for non-mutually-exclusive choices
- Include "Other" automatically (tool handles this)
- Use short headers (max 12 chars)

### Adaptive Branching Rules

Skip categories based on context:
- **Internal tool**: Skip pricing/revenue questions in Business & Value
- **Backend-only**: Minimize UX & Design category
- **Bug fix**: Focus on Problem & Context, Technical, Testing
- **Feature**: Full interview but lighter on Busine