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.
From pm-product-discoverynpx claudepluginhub tarunccet/pm-skills --plugin pm-product-discoveryThis skill uses the workspace's default tool permissions.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.
| Input | Required? | Example |
|---|---|---|
| Interview transcript | ✅ Required | Raw text, PDF, or audio transcription |
| Product or discovery context | ✅ Required | What product area or hypothesis was being explored |
| Interviewee type | 🟡 Recommended | Enterprise buyer, end user, churned customer |
| Research questions the interview was trying to answer | ⚪ Optional | "Why do users abandon setup?" |
Don't have everything? Start anyway — the skill will work with what you provide and flag where richer input would improve the output.
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.
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.
**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, Tarun Narang, Follow up with customer about pricing"]
Save the summary as a markdown document in the user's workspace.