phuryn/summarize-interview
pm-product-discovery/skills/summarize-interview/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills summarize-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 2:54 PM61.8s1 file scanned
SKILL.md
- 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.
Further Reading
- User Interviews: The Ultimate Guide to Research Interviews
- Continuous Product Discovery Masterclass (CPDM) (video course)
Related Skills
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
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.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
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.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026