# Claude Skills Templates for PMs ## Skill 1: Customer Interview Synthesis ### SKILL.md ``` name: interview-synthesis description: Synthesize customer interview transcripts into structured insights. Trigger when you see: interview, transcript, customer conversation, user research, synthesis, feedback session. ## What to extract 1. Key pain points (ranked by emotional intensity) 2. Unmet needs (things they're working around) 3. Quotes worth saving (verbatim, with context) 4. Opportunity mapping suggestions (connect to known product gaps) 5. Surprises (things that challenge our assumptions) ## Format - Lead with the 3 most important insights - Group pain points by theme - Include direct quotes with context - End with "What to explore next" section ## Tone - Analytical but human - No jargon - Focus on the "why" behind what people said ``` --- ## Skill 2: PRD / One-Pager ### SKILL.md ``` name: product-one-pager description: Draft or edit product specs, PRDs, one-pagers, and proposals. Trigger when you see: draft, spec, PRD, one-pager, proposal, product plan, brief, feature spec. ## Template structure 1. PROBLEM: Who are we building for and what problems are we solving? 1-3 user pain points. Include customer quotes or data if available. 2. VISION: One sentence describing the end state. Start with a verb. Inspiring, actionable, concise. 3. PRINCIPLES: 3-4 guiding rules for how we'll build. Help the team make independent decisions. 4. GOALS: One output metric (what success looks like) + 2-3 input metrics (levers we control). 5. SOLUTION: Clear steps of what we want to build. 1-2 sentences each. Answer: why will we win? 6. NOT PRIORITIZING: What we're NOT doing and why. 7. FAQ (optional): 2-3 expected objections addressed. ## Format - One page max - Short paragraphs, no walls of text - Bold key decisions - Link to supporting data, don't inline it ## Tone - Confident and direct - No hedging (avoid: should, might, could, probably) - Every sentence earns its place ``` ### resources/strategy-memo.md ``` Use this template for strategy documents and one-pager plans. PROBLEM [Who are we building for? What's broken for them?] - Pain point 1: [specific, with data or quote] - Pain point 2: [specific, with data or quote] - Pain point 3: [specific, with data or quote] VISION [One sentence. Verb first. Inspiring + actionable + concise.] PRINCIPLES 1. [Principle]: [Why this guides our decisions] 2. [Principle]: [Why this guides our decisions] 3. [Principle]: [Why this guides our decisions] GOALS - Output metric: [What success looks like, measurable] - Input metric 1: [Lever we control] - Input metric 2: [Lever we control] - Input metric 3: [Lever we control] SOLUTION Step 1: [What we build first and why] Step 2: [What comes next and why] Step 3: [What follows and why] Why we win: [1-2 sentences] NOT PRIORITIZING - [Thing we're skipping]: [Why] - [Thing we're skipping]: [Why] FAQ Q: [Expected objection] A: [Direct answer] ``` --- ## Skill 3: Stakeholder Update ### SKILL.md ``` name: stakeholder-update description: Generate concise stakeholder updates and status reports. Trigger when you see: update, status, weekly report, stakeholder, progress report, executive summary. ## Format ### What shipped this week - [Feature/fix]: [One sentence impact] ### In progress - [Initiative]: [Status, ETA, any blockers] ### Key metrics - [Metric]: [Current] → [Target] ([trend]) ### Blockers - [Blocker]: [What's needed to unblock] ### Next week - [Priority 1] - [Priority 2] ## Rules - Max 200 words total - Lead with wins - Be specific about blockers (who needs to do what) - Metrics always include trend direction - No fluff, no "great progress" without specifics ``` --- ## Skill 4: Competitive Intel ### SKILL.md ``` name: competitive-intel description: Structure competitive analysis and market intelligence. Trigger when you see: competitor, competitive, market analysis, positioning, competitive landscape, market intel. ## Analysis structure 1. WHAT HAPPENED: What did the competitor launch/announce/change? 2. WHY IT MATTERS: How does this affect our customers and positioning? 3. OUR GAP: Where are we ahead and behind now? 4. RECOMMENDED RESPONSE: What should we do (or not do)? 5. TIMELINE: How urgent is this? ## Rules - Be specific about features, not vague about "innovation" - Always tie back to customer impact - Distinguish between real threats and noise - Include source links where possible - Don't panic, most competitor moves matter less than they seem ``` --- ## Skill 5: OKR / Outcome Tracking ### SKILL.md ``` name: okr-tracker description: Help draft, refine, and track OKRs and outcome metrics. Trigger when you see: OKR, outcome, metric, goal, quarterly planning, key result, objective. ## OKR format Objective: [Qualitative, what you want to achieve] - KR1: [Measurable, from X to Y by when] - KR2: [Measurable, from X to Y by when] - KR3: [Measurable, from X to Y by when] Initiatives: - [What you'll do to move KR1] - [What you'll do to move KR2] - [What you'll do to move KR3] ## Quality checks - Is the objective inspiring? (Would the team rally around it?) - Are key results measurable? (Can you check progress weekly?) - Are they outcomes, not outputs? ("Increase retention" not "Ship feature X") - Is 70% achievement the sweet spot? (Not too easy, not impossible) - Do initiatives clearly ladder to key results? ## Common mistakes to flag - Output disguised as outcome ("Launch new onboarding" → "Increase Day 7 activation from 30% to 50%") - Too many KRs (max 3-4 per objective) - KRs that don't ladder to the objective - Missing baseline numbers - Vanity metrics (page views, sign-ups without activation) ``` --- ## Setup instructions 1. Create a folder for each skill (e.g., `interview-synthesis/SKILL.md`) 2. Zip the folder and upload to Claude Settings → Capabilities → Skills 3. Add to your custom instructions: "Always check /mnt/skills/user/ for applicable skills before responding." 4. Test each skill in a new conversation with relevant trigger words