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)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
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.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.