summarize-interview
Summarize Interview transforms customer interview transcripts into structured discovery documents organized around Jobs to Be Done, satisfaction levels, problems, and action items. Use this skill when processing interview recordings, synthesizing discovery sessions, or creating standardized summaries for product teams who need consistent synthesis of customer research.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/summarize-interview && cp -r /tmp/summarize-interview/pm-product-discovery/skills/summarize-interview ~/.claude/skills/summarize-interviewSKILL.md
## Summarize Customer Interview Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items. ### Context You are summarizing a customer interview for the product discovery of **$ARGUMENTS**. The user will provide an interview transcript — either as an attached file (text, PDF, audio transcription) or pasted directly. Read any attached files first. ### Instructions 1. **Read the full transcript** carefully before summarizing. 2. **Fill in the summary template** below. Use "-" if information is unavailable. Replace numeric values with qualitative descriptions if needed (e.g., "not satisfied"). 3. **Use clear, simple language** — a primary school graduate should be able to understand the summary. ### Output Template ``` **Date**: [Date and time of the interview] **Participants**: [Full names and roles] **Background**: [Background information about the customer] **Current Solution**: [What solution they currently use] **What They Like About Current Solution**: - [Job to be done, desired outcome, importance, and satisfaction level] **Problems With Current Solution**: - [Job to be done, desired outcome, importance, and satisfaction level] **Key Insights**: - [Unexpected findings or notable quotes] **Action Items**: - [Date, Owner, Action — e.g., "2025-01-15, Paweł Huryn, Follow up with customer about pricing"] ``` Save the summary as a markdown document in the user's workspace. --- ### Further Reading - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.