summarize-interview

Summarize research interview transcripts into structured discovery synthesis with insights and action items.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill summarize-interview-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: summarize-interview
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/pm-skills/summarize-interview
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill summarize-interview-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw interview transcripts are long and unstructured, making it hard to turn customer conversations into usable discovery evidence. This Skill converts a full transcript into a consistent, structured synthesis that feeds personas, journey maps, and value propositions. ## Core Features & Use Cases - Structured Synthesis Template: Captures date, participants, background, current solution, what works, problems, key insights, and dated action items with owners. - Jobs-to-be-Done Framing: Records each job, desired outcome, importance, and satisfaction for both what works and what does not. - Raw-Transcript-Only Rule: Works only from the raw transcript, never from a tool's auto-generated summary, and scrubs cross-project details from action items. - Use Case: After a 45-minute discovery call with a customer, paste the transcript and receive a markdown summary with insights and assigned action items ready to share with the team. ## Quick Start Summarize this customer interview transcript into the structured discovery template with key insights and dated action items.

Frequently Asked Questions about summarize-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize a customer interview transcript?▼

Read the full raw transcript, then fill the structured template: date, participants, background, current solution, what works, problems, key insights, and action items with dates and owners. Save the result as markdown so it can feed personas and journey maps.

What should a discovery interview summary include?▼

Include interview date, participant names and roles, background, the current solution, what works and what does not framed as jobs to be done with importance and satisfaction, key insights or notable quotes, and dated action items with owners.

Can I summarize an interview from an auto-generated transcript summary?▼

No. This method requires working only from the raw transcript, never a tool's auto-produced summary or action list, because those tools cannot tell which project or client a remark belongs to. Synthesize directly from the transcript.

When should I not use interview synthesis?▼

Do not use it for meeting debriefs; it is designed for research interviews only. Also avoid it when you lack the raw transcript, since summaries built from secondary tool outputs lose project-specific context.

How do I handle confidential interview data in summaries?▼

Keep the transcript and summary within your own handling boundaries and do not route them to another channel without explicit confirmation. Scrub any action item details that belong to a different project before sharing the output.