From pm-copilot
Use this skill when the user asks to "synthesize interview notes", "analyze my user interviews", "what patterns are in my interviews", "help me with continuous discovery", "find the themes in these interviews", "what did I learn from these calls", "turn these interview notes into opportunities", or pastes or shares raw interview transcripts or notes from user conversations. This skill focuses on the interview synthesis step of continuous discovery, not general feedback analysis — use feedback-triage for support tickets or NPS data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:continuous-interview-synthesisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are synthesizing user interview notes into opportunities using Teresa Torres' continuous discovery methodology. The goal is to extract struggles and unmet needs — not feature requests — and connect them to OST opportunities.
You are synthesizing user interview notes into opportunities using Teresa Torres' continuous discovery methodology. The goal is to extract struggles and unmet needs — not feature requests — and connect them to OST opportunities.
Key principle from Torres: "The most common interview mistake is asking users what they want. Instead, ask about their past behavior. Reconstruct the experience." — Teresa Torres
Read memory/user-profile.md and context/product/personas.md. Understand: what desired outcome is this discovery work in service of? What OST opportunities already exist?
Identify what's been provided:
If the interviewee context is missing, note it — segment-level patterns matter more than individual quotes.
For each interview, extract:
For any interview that touched on when or why the user adopted your product (or a competitor), apply the switch interview pattern:
This surfaces JTBD insights from the interview data.
Group interview moments across all transcripts by underlying struggle. A cluster becomes an opportunity when:
Name each opportunity as: "Users struggle to [action] when [context]"
For each opportunity, capture:
Map the opportunities into the existing OST structure (if one exists in memory or context). If no OST exists, create one.
Check: do any of the interview opportunities suggest sub-opportunities under existing OST nodes? Do any suggest the current OST is missing a major opportunity branch?
Evaluate the quality of the interview data:
Flag any quality concerns and recommend what additional interviews would strengthen weak signals.
Produce a structured synthesis:
Offer to save findings to memory/user-profile.md and update the persona file with new insights.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultySynthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions.
Transforms user interview transcripts into structured research findings with themed synthesis, supporting quotes, product implications, and next steps.