product-design

# Product Design

Interview users to extract implementation-ready requirements, then produce a PRD with enough detail to build with minimal ambiguity.

## Interview Workflow

### Phase 1: Core Concept (always)

Start here. Get the essential shape of the product.

1. **What is it?** One sentence describing what the app does
2. **Who uses it?** Primary user roles (2-4 max for MVP)
3. **Core actions?** What can each role do? (aim for 3-5 key actions per role)
4. **Platform?** Web, mobile, both? Any platform constraints?

Exit when: You can explain the app to someone in 30 seconds.

### Phase 2: User Scenarios (always)

For each role, define concrete scenarios at the feature level.

For each key action, ask:
- "Walk me through exactly what happens when [role] does [action]"
- "What information do they need to see? What do they input?"
- "What happens after? Where do they end up?"

Probe for edge cases:
- "What if [input is missing/invalid]?"
- "What if [user cancels midway]?"
- "Are there limits? (max items, required fields, etc.)"

Exit when: You could sketch every screen and know what each button does.

### Phase 3: Technical Context (always)

Nail down the tech stack. The PRD should specify exactly what to build with.

| Topic | Key questions |
|-------|---------------|
| **Frontend** | Web app, mobile (React Native, Flutter, native), or both? Which framework (React, Vue, Next.js, etc.)? |
| **Backend** | BaaS (Supabase, Firebase, Convex)? Custom API (Node, Python, Go)? Serverless functions? |
| **Database** | Postgres, MongoDB, SQLite? Managed by BaaS or self-hosted? |
| **Deployment** | Vercel, Netlify, Railway, Fly.io? App stores for mobile? |
| **Auth** | Built-in (Supabase Auth, Firebase Auth)? Third-party (Auth0, Clerk)? Social providers needed? |
| **Integrations** | Which external services? What data flows between? |
| **Payments** | Stripe, RevenueCat? Subscription vs one-time? |
| **Notifications** | Email (Resend, SendGrid)? Push? What triggers them? |
| *