derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage…
Prepare a customer interview script or summarize an interview transcript into structured insights
> /plugin marketplace add phuryn/pm-skillsHow it fires
How this command gets triggered: by you, by Claude, or both.
/interviewContext preview
What this command does when you run it.
Prepare a customer interview script or summarize an interview transcript into structured insights
description: Prepare a customer interview script or summarize an interview transcript into structured insights argument-hint: "[prep|summarize] <topic or transcript>"
Two modes: **prep** creates a structured interview script before you talk to customers, **summarize** extracts insights after you've done the interview.
/interview prep Onboarding experience for enterprise users /interview summarize [paste transcript or upload file] /interview # asks which mode you need
---
Create a structured interview script tailored to your research question.
**Step 1: Understand the Research Goal**
Ask the user:
**Step 2: Generate Interview Script**
Apply the **interview-script** skill:
## Interview Script: [Research Topic] **Research Question**: [what we're trying to learn] **Target Participant**: [who] **Duration**: [X] minutes ### Warm-up (3-5 min) [Rapport-building questions, role/context understanding] ### Core Exploration (15-40 min) [JTBD probing, past behavior, current workflow, pain points] - For each question: the question + why you're asking it + follow-up prompts ### Specific Topics (5-10 min) [Targeted questions about specific features or concepts — if needed] ### Wrap-up (3-5 min) [Open-ended closing, referral ask, next steps] ### Note-Taking Template [Pre-formatted template to capture insights during the interview] ### Red Flags to Watch For [Signs the conversation is going off-track or the participant is being polite rather than honest]
**Step 3: Customize and Review**
---
Transform an interview transcript into structured, actionable insights.
**Step 1: Accept the Transcript**
Accept in any format:
If the input is rough notes rather than a full transcript, work with what's available and note the limitations.
**Step 2: Extract and Structure**
Apply the **summarize-interview** skill:
Parse the transcript to identify:
**Step 3: Generate Interview Summary**
## Interview Summary **Participant**: [anonymized profile — role, segment, experience] **Date**: [if known] **Duration**: [if known] **Interviewer**: [if known] ### Key Insights 1. **[Insight]** — [supporting evidence/quote] 2. **[Insight]** — [supporting evidence/quote] 3. ... ### Jobs to Be Done - **Primary JTBD**: [When I..., I want to..., so I can...] - **Related JTBDs**: [additional jobs] ### Current Workflow [How the participant currently solves the problem, step by step] ### Pain Points | Pain Point | Severity | Quote | |-----------|----------|-------| ### Satisfaction Signals | What Works | Why | Quote | |-----------|-----|-------| ### Notable Quotes > "[quote]" — on [topic] ### Assumptions Validated / Invalidated | Assumption | Status | Evidence | |-----------|--------|----------| ### Action Items - [ ] [Follow-up action from this interview] - [ ] [Research question to explore further] ### Raw Notes [If helpful, include annotated key sections]
Save the summary as a markdown file.
**Step 4: Connect to Broader Research**
Offer:
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage…
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus…
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by…
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed…
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage,…
Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends