summarize-interview

phuryn/pm-skills

Transform interview transcripts into structured summaries with JTBD, satisfaction signals, and action items.

What is summarize-interview?

Summarize customer interview transcripts into a structured template that captures Jobs to Be Done, satisfaction levels, key insights, and action items. Use this when processing interview recordings, synthesizing discovery interviews, or creating standardized interview summaries for product discovery.

Parses interview transcripts (text, PDF, or audio transcription) into a structured format
Extracts and organizes Jobs to Be Done with desired outcomes and satisfaction levels
Identifies problems with current solutions and their importance
Captures unexpected findings and notable quotes as key insights
Generates action items with dates and owners for follow-up tasks
Outputs summaries as markdown documents in your workspace

How to install summarize-interview

npx skills add https://github.com/phuryn/pm-skills --skill summarize-interview

Claude Code

Cursor

Windsurf

Cline

How to use summarize-interview

1.Provide an interview transcript (paste directly, upload text file, PDF, or audio transcription)
2.The skill reads the full transcript carefully
3.The skill fills in the structured summary template with date, participants, background, current solution, likes, problems, key insights, and action items
4.Review the generated markdown summary in your workspace
5.Share or reference the summary for product decisions and follow-ups

Use cases

Good for

Processing customer discovery interview recordings and transcripts
Synthesizing multiple interviews into standardized summaries for product teams
Creating structured records of user research for product decision-making
Extracting actionable insights from customer conversations for roadmap planning
Documenting satisfaction signals and pain points for feature prioritization

Who it's for

Product managers conducting customer discovery
User researchers synthesizing interview data
Product teams analyzing customer feedback
Startup founders gathering customer insights

summarize-interview FAQ

What file formats are supported?

Text files, PDFs, and audio transcriptions. You can also paste transcripts directly.

What if information is missing from the transcript?

The template uses '-' to indicate unavailable information. Qualitative descriptions replace numeric values when needed.

How should action items be formatted?

As date, owner, and action description (e.g., '2025-01-15, Paweł Huryn, Follow up with customer about pricing').

Can this handle multiple interviews at once?

Process one interview transcript at a time. For multiple interviews, run the skill separately for each and compare summaries.

What language should the summary use?

Clear, simple language that a primary school graduate can understand—avoid jargon.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.

name: summarize-interview description: "Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries."

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

Read the full transcript carefully before summarizing.
Fill in the summary template below. Use "-" if information is unavailable. Replace numeric values with qualitative descriptions if needed (e.g., "not satisfied").
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.