summarize-interviewlisted

# Summarise Interview ## Usage **When to use:** Immediately after any customer call, while the call is fresh. **Inputs:** Transcript, raw notes, or verbal description. **Output:** Structured note saved to `knowledge/customers/interviews/`. **Template:** `templates/discovery-notes.md` The goal is zero friction between "call ends" and "knowledge is in the repo." A note written in the moment is 10× more useful than one reconstructed from memory three days later. Don't wait until you have a full transcript — raw notes are fine. --- ## THINK: Choose depth mode | Call type | Mode | |---|---| | Discovery / switch / usability / retention interview | **Full synthesis** — JTBD, BEAM, Forces of Progress, signal quality | | Check-in / sales call / churn conversation / validation | **Quick capture** — 5 core sections, no deep frameworks | Confirm before starting: 1. **Customer name or pseudonym** — use first name or company name; never store full names in the repo 2. **Call type** — discovery / validation / check-in / churn / sales / other 3. **Input format** — timestamped transcript, bullet notes, or verbal summary? If the input is a raw transcript, extract signal; don't summarise chronologically. The transcript is the record — the note is the analysis. --- ## QUICK CAPTURE MODE For check-ins, sales calls, churn conversations, and non-discovery sessions. Read `templates/discovery-notes.md` and use it as the output structure, applying only the sections relevant to this call typ