# Customer Call To Prd

> Use when converting customer call notes, interview transcripts, sales discovery notes, or PM research fragments into a concise PRD with user problems, requirements, non-goals, and risks.

- Skill: `alexzhu0/customer-call-to-prd` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alexzhu0/customer-call-to-prd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexzhu0/customer-call-to-prd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: alexzhu0 (https://skillmd.com/u/alexzhu0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexzhu0/customer-call-to-prd

---


# 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.