Summarize Interview
Turn raw customer interview transcripts into a JTBD-focused summary your agent can reuse in discovery docs.
Overview
Summarize-interview is an agent skill most often used in Idea (also Validate) that turns customer interview transcripts into a structured JTBD summary with satisfaction signals and action items.
Install
npx skills add https://github.com/phuryn/pm-skills --skill summarize-interviewWhat is this skill?
- Maps transcripts to a fixed template: date, participants, background, current solution
- Captures jobs-to-be-done with importance and satisfaction for likes and pain points
- Uses plain language so summaries are readable beyond the product team
- Marks missing fields with "-" instead of inventing quotes or metrics
- Reads attached files or pasted text before filling the template
Adoption & trust: 1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finished discovery interviews but still have an unreadable transcript instead of a shareable JTBD summary.
Who is it for?
Solo builders running lightweight customer discovery who want agent-assisted synthesis from transcripts or attachments.
Skip if: Teams that already have a signed spec and only need implementation tasks—use planning or build skills instead.
When should I use this skill?
Processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries.
What do I get? / Deliverables
You get a filled interview template with current solution, likes, problems, and action items ready to drop into discovery notes or specs.
- Structured interview summary with JTBD, satisfaction, and action items
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Customer interviews are the canonical shelf for Idea-phase research before you lock scope or build. Structured interview synthesis belongs on the research subphase where transcripts become audience and problem insight.
Where it fits
After five discovery calls, you paste transcripts and generate comparable JTBD summaries for a positioning doc.
You summarize interviews to clarify who struggles with the current workaround and how satisfied they are.
You distill interview pain points into scoped problems before writing a prototype brief.
You refresh interview summaries when backlog items need traceability back to customer quotes.
How it compares
Structured interview template for discovery, not a generic meeting-notes summarizer.
Common Questions / FAQ
Who is summarize-interview for?
Solo and indie product builders processing customer or user interviews during discovery for a specific product initiative.
When should I use summarize-interview?
Use it in Idea/research when synthesizing discovery transcripts, and in Validate/scope when turning interview evidence into scoped problem statements before you commit to a build.
Is summarize-interview safe to install?
Treat transcripts as sensitive; review the Security Audits panel on this page and avoid piping confidential audio or PII into untrusted agents without your own policy checks.
SKILL.md
READMESKILL.md - Summarize Interview
## 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)