customer-call-to-prdlisted

# Customer Call To PRD ## Purpose Transform customer conversation material into a product requirement draft that preserves evidence and uncertainty. ## Fit - Use when customer research needs to become requirements without losing the original evidence. - Do not use when the user already has a finalized PRD and only needs copyediting. ## Inputs - Call notes, transcript snippets, interview notes, or sales discovery notes. - Customer segment, product area, and known business goal if available. - Existing constraints, deadlines, or roadmap context. ## Workflow 1. Extract user problems before proposing features. 2. Separate direct customer evidence from internal interpretation. 3. Group repeated needs into requirements. 4. Define non-goals to prevent scope creep. 5. Add risks, dependencies, and open questions for PM follow-up. ## Output Produce Markdown with: - Customer Context - Problem Statements - Requirements - Non-Goals - Evidence - Risks And Dependencies - Open Questions ## Validation - Requirements trace back to call evidence. - Internal guesses are labeled as interpretation. - Non-goals are explicit. - The PRD does not promise delivery dates unless provided. - Open questions are specific enough for a follow-up call.