From role-pm
Synthesize a batch of user or customer interviews — from Fathom recordings, transcripts, or notes — into themes, patterns, quotes, and contradictions. Produces a structured synthesis doc. Drafts only.
npx claudepluginhub sitloboi2012/team-marketplace --plugin role-pmThis skill uses the workspace's default tool permissions.
**Invocation: user only.** Produces a synthesis artifact — doesn't publish without approval.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Share bugs, ideas, or general feedback.
Invocation: user only. Produces a synthesis artifact — doesn't publish without approval.
Takes N user interviews and produces a doc that turns raw listening into signal. A good synthesis surfaces patterns the PM didn't already see and grounds them in specific quotes.
From $ARGUMENTS, identify the set:
If Fathom MCP isn't connected, or the user points at external transcripts, ask for links or content.
For each interview via Fathom MCP:
If the batch is large (>8 interviews), do this in a forked subagent context to avoid flooding.
Per interview, extract:
Group observations that recur. A theme needs:
Also track:
If the interview set crosses segments (e.g. new users vs power users, SMB vs enterprise), break themes by segment where it matters. Not every theme needs segmentation — only when the pattern actually differs.
# Interview synthesis: <topic or batch name>
**Interviews:** N · **Window:** <date range> · **Segments:** <if relevant>
## TL;DR
<3 sentences. The single biggest pattern and the single biggest surprise.>
## Themes
### Theme 1: <one-sentence articulation>
**Evidence:** N interviews
**Quotes:**
> "<direct quote>" — <participant role, interview date>
> "<direct quote>" — <participant role, interview date>
**What it suggests:** <1-2 sentences, descriptive not prescriptive>
### Theme 2: ...
(Aim for 3-7 themes. If you have more, they're not clustered tightly enough.)
## Contradictions
- **<dimension>**: Some users said <X>, others said <Y>. The split appears to track <segment / usage pattern / etc.>.
## Surprises
- <singleton observation, interesting, worth noting>
## Unchanged assumptions
<Assumptions we walked in with that the interviews did NOT change. Worth stating — it tells the reader which of the PM's existing hypotheses survived.>
## What the interviews do NOT tell us
<Explicit. "These interviews were with existing users, so they tell us nothing about why non-users don't sign up." Honest scoping keeps the synthesis from being over-applied.>
## Recommendations (optional section — only if the user asks)
1. <specific, grounded in themes>
2. ...
Show the synthesis. Common edits:
On approval: