domains / research / interview-summary / summarize-interview

summarize-interview

Skill card

combined

Both copies summarize a single interview transcript, but they use different output structures and constraints. The phuryn copy is JTBD-centric with a fixed template (Current Solution, What They Like, Problems, Key Insights, Action Items) and a plain-language requirement. The Owl-Listener copy is theme-centric with participant profile, 3-5 themes, pain points with severity, workarounds, delighters, 5-8 verbatim quotes, surprises, and a confidence rating for each insight. Neither is a strict reproduction of the other, so crowning one would hide a real alternative.

Repositories

Other copies

Combined skill

---
name: summarize-interview
description: "Summarize a single customer or user interview transcript into a structured document with themes, JTBD, satisfaction signals, quotes, and action items. Use immediately after a session. For synthesizing many sessions, use an affinity-diagram skill."
---

# Summarize Interview

Transform one interview transcript into a structured, actionable summary.

## Context

You are summarizing an interview transcript for $ARGUMENTS. The user will provide the transcript 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.
3. **Use clear, simple language** — a primary school graduate should be able to understand the summary.
4. **Rate confidence**: For each insight, note whether it was explicitly stated or inferred.
5. Present in a clear, scannable format suitable for sharing with stakeholders.

## Output Template

```
**Date**: [Date and time of the interview]
**Participants**: [Full names and roles]
**Background / Participant profile**: [Role, context, experience level, background information]

**Current Solution / Workarounds**: [What solution they currently use and how they solve problems]

**Key Themes** (3-5):
- [Theme] — [Supporting quote] — [Confidence: explicit/inferred]

**Jobs-to-be-done**:
- [Job to be done, desired outcome, importance, satisfaction level]

**What They Like / Delighters**:
- [Job to be done, desired outcome, importance, satisfaction level]

**Problems / Pain Points**:
- [Job to be done, desired outcome, importance, satisfaction level, severity]

**Notable Quotes** (5-8 verbatim):
- [Quote]

**Surprises / 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.

## Conflicts

- phuryn/pm-skills uses a fixed JTBD template; Owl-Listener/designer-skills uses a theme-based structure. This combined template merges both.
- phuryn/pm-skills requires plain language; Owl-Listener/designer-skills does not. The combined instruction keeps the plain-language constraint.
- Owl-Listener/designer-skills requires a confidence rating; phuryn/pm-skills does not. The combined instruction includes the confidence rating.
- Owl-Listener/designer-skills requires 5-8 verbatim quotes; phuryn/pm-skills does not specify a count. The combined instruction includes the 5-8 quote requirement.