From d7ef6a1e538aadf7e668bfe998441c0b30404daf Mon Sep 17 00:00:00 2001 From: mohitagw15856 <119053560+mohitagw15856@users.noreply.github.com> Date: Thu, 29 Jan 2026 08:28:36 +0000 Subject: [PATCH] Add files via upload --- pm-skills-action-plan.md | 293 ++++++++++ pm-skills-examples-part1.md | 644 +++++++++++++++++++++ pm-skills-examples-part2.md | 1043 +++++++++++++++++++++++++++++++++++ 3 files changed, 1980 insertions(+) create mode 100644 pm-skills-action-plan.md create mode 100644 pm-skills-examples-part1.md create mode 100644 pm-skills-examples-part2.md diff --git a/pm-skills-action-plan.md b/pm-skills-action-plan.md new file mode 100644 index 0000000..2f1599f --- /dev/null +++ b/pm-skills-action-plan.md @@ -0,0 +1,293 @@ +# Action Plan: Sharing Your Product Management Skills + +## Overview +You've got significant traction on your Medium article about Claude Skills, and readers are asking to access your actual Skills. This plan outlines how to package, share, and potentially monetize these Skills effectively. + +## Phase 1: Immediate Actions (Week 1) + +### 1.1 Create GitHub Repository Structure +``` +pm-claude-skills/ +├── README.md +├── LICENSE +├── CONTRIBUTING.md +├── skills/ +│ ├── prd-template/ +│ ├── user-research-synthesis/ +│ ├── stakeholder-update/ +│ ├── meeting-notes/ +│ ├── competitive-analysis/ +│ ├── data-analysis-standard/ +│ └── roadmap-presentation/ +├── examples/ +│ ├── prd-example.md +│ ├── research-synthesis-example.md +│ └── stakeholder-update-example.md +├── docs/ +│ ├── installation.md +│ ├── customization-guide.md +│ └── skill-creation-tutorial.md +└── .github/ + ├── ISSUE_TEMPLATE/ + └── PULL_REQUEST_TEMPLATE/ +``` + +### 1.2 Prepare Your First 3-5 Skills +Start with your most popular/useful Skills from the article: +1. **PRD Template** - High demand, universal PM need +2. **User Research Synthesis** - Differentiating capability +3. **Stakeholder Update** - Immediate time-saver +4. **Meeting Notes** - Easy win, broad applicability +5. **Competitive Analysis** - Ongoing value + +### 1.3 Write Compelling README +Your README should include: +- Hook referencing your viral Medium article +- Clear value proposition +- Quick start guide (5 minutes to first skill) +- Skill catalog with descriptions +- Installation instructions +- Examples of before/after +- Link back to your Medium article for context +- Call-to-action (star the repo, follow for updates) + +## Phase 2: Monetization Strategy (Week 2-3) + +### Option A: Freemium Model (Recommended) +**Free tier:** +- 3-5 foundational Skills (PRD, Meeting Notes, Stakeholder Update) +- Basic documentation +- Community support via GitHub Issues + +**Premium tier ($29-49 one-time or $9-19/month):** +- Complete Skills library (15-20 Skills) +- Advanced Skills (Quarterly Planning, Product Launch, Go-to-Market) +- Domain-specific Skills (SaaS, B2B, Consumer) +- Priority support +- Regular updates and new Skills +- Private Discord/Slack community +- 1:1 customization consultation (higher tiers) + +**Platform options:** +- Gumroad (simple, low fees, good for digital products) +- GitHub Sponsors (integration with repo, recurring revenue) +- Lemon Squeezy (modern, tax handling, international) +- Patreon (recurring, community features) + +### Option B: Fully Open Source with Support Model +- All Skills free and open source (MIT or Apache 2.0) +- Monetize through: + - GitHub Sponsors for ongoing development + - Consulting for custom Skills ($200-500/hour) + - Team workshops ($2000-5000) + - Corporate licenses with support SLA + +### Option C: Tiered Product Bundles +- **Starter Pack** ($19): 5 essential Skills +- **Professional Pack** ($49): 12 Skills + templates +- **Team Pack** ($199): 20 Skills + customization guide + group license +- **Enterprise Pack** ($999): Everything + consultation + custom Skills + +## Phase 3: Marketing & Distribution (Ongoing) + +### 3.1 Update Your Medium Article +Add a section at the end: +```markdown +## Get the Skills I Use Daily + +Many readers have asked to access the actual Skills I described in this article. +I've packaged them up and made them available on GitHub: + +🔗 [github.com/yourname/pm-claude-skills](link) + +The repository includes: +- 5 free essential PM Skills to get started +- Detailed installation and customization guides +- Real examples from my daily workflow +- A growing library of specialized Skills + +Star the repo to get updates as I add new Skills based on reader feedback. +``` + +### 3.2 Create Follow-Up Content +**Medium articles:** +- "How to Install and Customize PM Skills for Claude" (technical guide) +- "5 Claude Skills Every Product Manager Should Use" (listicle for reach) +- "Building Your Own Claude Skills: A PM's Guide" (educational) +- "3 Months Using Claude Skills: Productivity Results" (case study) + +**Other platforms:** +- Twitter/X threads showcasing specific Skills +- LinkedIn posts with before/after examples +- YouTube video walkthrough (if comfortable) +- Product Hunt launch for visibility + +### 3.3 Community Building +- Enable GitHub Discussions for Q&A +- Create #claude-skills channel if you have a Slack/Discord +- Respond to all Issues/PRs promptly (community goodwill) +- Share user success stories and customizations +- Monthly "Skill of the Month" spotlights + +## Phase 4: Product Development (Month 2+) + +### 4.1 Expand the Library +Based on reader feedback and demands: +- Domain-specific Skills (healthcare PM, fintech PM, B2B SaaS PM) +- Role-specific Skills (senior PM, PM lead, growth PM) +- Company-stage Skills (startup PM, enterprise PM) +- Industry frameworks (JTBD Skills, Jobs-to-be-Done) + +### 4.2 Create Companion Products +- **Skill Builder Tool**: Interactive tool to generate custom Skills +- **Templates Pack**: Notion/Confluence templates that match your Skills +- **Video Course**: "Mastering Claude Skills for Product Management" +- **Book/Guide**: "The AI-Powered PM" (extended content) + +### 4.3 Enterprise Offerings +- Custom Skill development services +- Team onboarding and training +- Organizational Skills library setup +- Integration consulting for Team/Enterprise Claude plans + +## Quick Start Implementation Checklist + +### This Weekend: +- [ ] Create GitHub repository +- [ ] Write README with clear value proposition +- [ ] Package 3 Skills (PRD, Meeting Notes, Stakeholder Update) +- [ ] Add installation instructions +- [ ] Include 1-2 before/after examples +- [ ] Choose a license (MIT recommended for adoption) + +### Next Week: +- [ ] Update Medium article with GitHub link +- [ ] Post announcement on LinkedIn/Twitter +- [ ] Set up monetization (choose Option A, B, or C) +- [ ] Create 2 additional Skills to build library +- [ ] Write follow-up Medium article + +### Month 1: +- [ ] Reach 100 GitHub stars (realistic goal) +- [ ] Get first 10 paying customers (if monetizing) +- [ ] Ship 2 more Skills based on feedback +- [ ] Create video walkthrough +- [ ] Build email list for updates + +## Pricing Recommendations + +Based on value provided and market positioning: + +**If going premium route:** +- **Individual Starter**: $29 one-time (5 essential Skills) +- **Individual Pro**: $49 one-time (12 Skills + updates for 1 year) +- **Individual Ultimate**: $19/month or $149/year (everything + ongoing) +- **Team License**: $199 (5 seats) or $499 (20 seats) + +**If going open source:** +- Suggested donation: $10-50 +- GitHub Sponsors tiers: $5, $15, $50, $200/month +- Custom Skills development: $500-2000 per Skill + +## Potential Revenue Projections + +**Conservative scenario (first 3 months):** +- 5,000 Medium article views +- 500 GitHub repo visits (10% conversion) +- 50 GitHub stars (10% engagement) +- 25 paying customers at $49 = $1,225 + +**Moderate scenario:** +- 10,000 Medium article views +- 1,500 GitHub repo visits +- 200 GitHub stars +- 100 paying customers = $4,900 +- 2 consulting engagements = $2,000 +- **Total: ~$7,000** + +**Optimistic scenario:** +- Viral Medium article (50k+ views) +- Product Hunt feature +- 1,000+ GitHub stars +- 500 paying customers = $24,500 +- 10 consulting engagements = $10,000 +- Enterprise pilot = $5,000 +- **Total: ~$40,000** + +## Legal Considerations + +### License Choice: +- **MIT License**: Most permissive, maximizes adoption +- **Apache 2.0**: Patent protection, corporate-friendly +- **Creative Commons BY-SA**: For documentation/examples only + +### Important Notes: +- Don't include proprietary company information in Skills +- Ensure examples are anonymized or fictional +- Add disclaimer that Skills are provided as-is +- Consider liability waiver for commercial use +- If using real data/examples, get permission + +## Success Metrics to Track + +### Week 1: +- GitHub stars +- Repository clones +- README views +- Issue/discussion engagement + +### Month 1: +- Total downloads/installs +- Paying customers (if applicable) +- Medium article referral traffic +- Community contributions (PRs, Issues) + +### Quarter 1: +- Monthly recurring revenue (if subscription) +- Skill usage patterns (via optional analytics) +- User testimonials and case studies +- Derivative works (others building on your Skills) + +## Risk Mitigation + +### Potential Issues: +1. **Skills stop working** (Claude updates): Maintain regularly +2. **Low adoption**: Invest in marketing and examples +3. **Support burden**: Set clear boundaries, community-driven +4. **Competition**: Focus on quality and PM-specific expertise +5. **Anthropic changes Skills format**: Stay close to updates + +## Next Steps + +**Immediate (today):** +1. Choose your monetization model +2. Decide on initial 3-5 Skills to share +3. Draft your README +4. Set up GitHub repository + +**This week:** +1. Package and upload Skills +2. Update Medium article +3. Announce on social media +4. Set up payment system (if monetizing) + +**This month:** +1. Engage with early users +2. Iterate based on feedback +3. Create follow-up content +4. Build towards 100 stars milestone + +--- + +## Recommended Starting Configuration + +**For maximum impact with minimal effort:** + +1. **Go with Option A (Freemium)** - Best balance of reach and revenue +2. **Use Gumroad** - Simplest payment setup +3. **Start with 5 free Skills** - Build trust and showcase quality +4. **Price premium at $49 one-time** - Accessible, substantial value perception +5. **Focus on GitHub + Medium** - Leverage existing audience +6. **Set aside 5 hours/week** - Sustainable maintenance + +Would you like me to help create specific Skills, write the README, or draft the announcement post? diff --git a/pm-skills-examples-part1.md b/pm-skills-examples-part1.md new file mode 100644 index 0000000..26219f8 --- /dev/null +++ b/pm-skills-examples-part1.md @@ -0,0 +1,644 @@ +# PM Claude Skills - Example Skills Package + +This document outlines the 7 Skills referenced in your Medium article that you can create and share. + +## Skill 1: PRD Template + +**File: `prd-template/SKILL.md`** + +```markdown +--- +name: prd-template +description: Product Requirements Document creation following proven PM template structure. Use when the user asks to create, write, draft, or help with a PRD, product requirements document, product spec, feature specification, or product documentation for a new feature or product. +--- + +# PRD Template Skill + +This skill helps create professional Product Requirements Documents following industry best practices. + +## Template Structure + +Every PRD should include these sections in order: + +### 1. Overview +- **Problem Statement**: What problem are we solving? (2-3 sentences) +- **Proposed Solution**: High-level description of what we're building (2-3 sentences) +- **Success Metrics**: How we'll measure success (3-5 key metrics) + +### 2. Context & Background +- **Why Now**: Why is this the right time? +- **Strategic Alignment**: How does this align with company objectives? +- **User Research Summary**: Key insights from research (if applicable) + +### 3. User Stories & Use Cases +Format: "As a [user type], I want to [action] so that [benefit]" +- Include 3-7 primary user stories +- Add acceptance criteria for each + +### 4. Requirements +**Functional Requirements:** +- Must-have features (P0) +- Should-have features (P1) +- Nice-to-have features (P2) + +**Non-Functional Requirements:** +- Performance expectations +- Security considerations +- Accessibility requirements + +### 5. Design & User Experience +- Link to design mocks or wireframes +- Key user flows +- Edge cases and error states + +### 6. Technical Considerations +- Architecture implications +- Dependencies on other systems +- Technical risks and mitigations + +### 7. Implementation Plan +- **Phase 1 (MVP)**: What goes in first version +- **Phase 2**: What comes next +- **Phase 3**: Future enhancements + +### 8. Open Questions +- Decisions that still need to be made +- Stakeholders to consult +- Research needed + +### 9. Appendix +- Research links +- Related documents +- Competitive analysis + +## Writing Guidelines + +**Tone**: Clear, concise, actionable +**Audience**: Engineers, designers, stakeholders +**Length**: Aim for 3-6 pages for features, 8-12 for products + +**Best Practices:** +- Use concrete examples over abstractions +- Include "why" not just "what" +- Make requirements testable +- Link to supporting materials +- Update as decisions are made + +## What Makes a Good PRD + +✅ **Do:** +- Write from the user's perspective +- Include specific success metrics +- Address edge cases +- Link to research and data +- Make trade-offs explicit + +❌ **Don't:** +- Write implementation details (that's tech spec) +- Assume everyone has context +- Leave requirements ambiguous +- Skip the "why" +- Forget about accessibility + +## Example PRD Opening + +``` +# PRD: Multi-Channel Customer Support Dashboard + +## Overview + +**Problem Statement**: Support teams are currently managing customer inquiries across email, chat, and social media using three separate tools, leading to delayed responses, duplicated work, and inconsistent customer experiences. On average, support agents waste 2.3 hours per day switching between tools and manually tracking conversation history. + +**Proposed Solution**: Build a unified dashboard that aggregates customer inquiries from all channels into a single interface, maintains conversation history across channels, and provides intelligent routing based on agent expertise and availability. + +**Success Metrics**: +- Reduce average response time from 4 hours to 1 hour +- Decrease tool-switching time by 80% (from 2.3 to <0.5 hours) +- Improve customer satisfaction score from 3.8 to 4.5 (out of 5) +- Increase support agent productivity by 35% +``` +``` + +--- + +## Skill 2: User Research Synthesis + +**File: `user-research-synthesis/SKILL.md`** + +```markdown +--- +name: user-research-synthesis +description: Analyze and synthesize user research findings following PM best practices. Use when the user provides user research data, interview transcripts, survey results, or user feedback that needs to be analyzed, synthesized, or summarized into insights and recommendations. +--- + +# User Research Synthesis Skill + +This skill helps analyze user research data and transform it into actionable insights following a structured methodology. + +## Synthesis Framework + +### 1. Data Collection Overview +- **Research Type**: Interviews, surveys, usability tests, etc. +- **Participant Profile**: Demographics, segments, sample size +- **Research Questions**: What we sought to learn +- **Methodology**: How data was collected + +### 2. Key Themes Identification + +Organize findings into themes using this structure: + +**Theme Name** +- **Description**: What this theme represents +- **Prevalence**: How many participants mentioned this (e.g., "8 out of 12 participants") +- **Supporting Quotes**: 2-3 representative quotes +- **Implication**: What this means for our product + +Aim for 4-8 major themes per research effort. + +### 3. Pain Points Analysis + +For each identified pain point: +- **Pain Point**: Clear description +- **Severity**: High/Medium/Low (based on impact and frequency) +- **Current Workaround**: How users deal with it today +- **Evidence**: Specific examples from research + +### 4. Feature Requests + +Categorize requests: +- **Must-Have**: Critical needs blocking user success +- **High Value**: Would significantly improve experience +- **Nice-to-Have**: Incremental improvements + +For each request: +- **Request**: What users asked for +- **Frequency**: How often it came up +- **User Quote**: Representative example +- **Underlying Need**: Why they want this (dig deeper than surface request) + +### 5. User Workflow Insights + +Document actual workflows observed: +- **Current State**: How users accomplish tasks today +- **Pain Points**: Where they struggle +- **Ideal State**: What they wish they could do +- **Opportunities**: Where we can add value + +### 6. Segmentation Insights + +If research reveals distinct user segments: +- **Segment Name**: Descriptive label +- **Characteristics**: What defines this segment +- **Unique Needs**: How their needs differ +- **Size/Importance**: Relative weight for prioritization + +### 7. Competitive Insights + +If users mentioned competitors or alternatives: +- **Competitor/Alternative**: What they use +- **Why They Use It**: What it does well +- **Gaps**: What it doesn't do +- **Switching Barriers**: Why they don't switch fully + +### 8. Recommendations + +Prioritized recommendations based on insights: + +**High Priority** +- Recommendation with supporting evidence +- Expected impact + +**Medium Priority** +- Recommendation with supporting evidence +- Expected impact + +**Low Priority / Future Consideration** +- Recommendation with supporting evidence +- Expected impact + +### 9. Open Questions + +Research gaps identified: +- What we still need to understand +- Suggested follow-up research +- Uncertainties requiring validation + +## Analysis Guidelines + +**When synthesizing interviews:** +- Look for patterns across multiple participants +- Note both what users say AND what they do +- Pay attention to emotional reactions +- Identify jobs-to-be-done, not just feature requests + +**When analyzing quotes:** +- Use verbatim quotes in "quotation marks" +- Attribute quotes: [Participant ID, Role, Context] +- Select quotes that illustrate patterns, not outliers +- Include both positive and negative feedback + +**When identifying themes:** +- Use descriptive names, not generic labels +- Provide evidence for each theme +- Quantify when possible ("7 out of 10 users...") +- Connect themes to business objectives + +## Quality Standards + +✅ **Good Synthesis:** +- Identifies patterns, not just individual responses +- Connects insights to product decisions +- Includes supporting evidence for each claim +- Separates observations from interpretations +- Prioritizes findings by impact + +❌ **Poor Synthesis:** +- Lists every individual comment +- Lacks evidence or examples +- Makes unsupported leaps +- Focuses on solutions before understanding problems +- Ignores contradictory data + +## Example Theme + +``` +**Theme: Information Overload During Onboarding** + +**Description**: Users consistently expressed feeling overwhelmed by the amount of information presented during initial setup, leading to incomplete onboarding and delayed time-to-value. + +**Prevalence**: 9 out of 12 participants mentioned this issue unprompted + +**Supporting Quotes**: +- "I just wanted to get started, but it felt like I needed to read a manual first" [P3, Marketing Manager] +- "By the third screen of instructions, I started clicking 'Next' without reading" [P7, Sales Rep] +- "I wish there was a 'quick start' option for people like me who just want to try it" [P11, Product Designer] + +**Implication**: Our current onboarding flow prioritizes completeness over engagement. We should consider a progressive disclosure approach where users can start using the product quickly and learn advanced features contextually. +``` +``` + +--- + +## Skill 3: Stakeholder Update + +**File: `stakeholder-update/SKILL.md`** + +```markdown +--- +name: stakeholder-update +description: Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives. +--- + +# Stakeholder Update Skill + +This skill creates effective status updates for executives and stakeholders following the BLUF (Bottom Line Up Front) principle. + +## Update Structure + +### 1. BLUF (Bottom Line Up Front) +Start with the most important information: +- **Status**: On track / At risk / Blocked / Complete +- **Key Takeaway**: One sentence summary of current state +- **Action Needed**: What you need from stakeholders (if anything) + +### 2. Progress Summary +Brief overview of accomplishments: +- What shipped this period +- Milestones achieved +- Key metrics movement + +Keep to 3-5 bullet points maximum. + +### 3. Metrics Dashboard + +**Key Metrics** +| Metric | Current | Target | Trend | Status | +|--------|---------|--------|-------|--------| +| [Metric name] | [Value] | [Target] | ↑/→/↓ | 🟢/🟡/🔴 | + +Include 3-5 most important metrics only. + +### 4. Risks & Blockers + +**High Priority Issues:** +- **Issue**: Brief description +- **Impact**: What's at stake +- **Mitigation**: What you're doing about it +- **Help Needed**: What stakeholders can do (if applicable) + +Only include issues that matter at executive level. + +### 5. Upcoming Milestones + +**Next 30 Days:** +- Milestone (expected date) +- Milestone (expected date) + +**Next 90 Days:** +- Major milestone (month) +- Major milestone (month) + +### 6. Decisions Needed (if applicable) +- **Decision**: Clear description +- **Options**: 2-3 options with pros/cons +- **Recommendation**: What you recommend and why +- **Timeline**: When decision is needed + +## Writing Guidelines + +**Tone**: Professional, concise, action-oriented +**Length**: Keep under 1 page (or 2 minutes reading time) +**Frequency**: Weekly for active projects, bi-weekly for maintenance + +**Executive Communication Principles:** + +1. **Lead with conclusions, not process** + - ❌ "We ran 5 experiments this week and analyzed the data..." + - ✅ "Conversion rate increased 15% from optimization work" + +2. **Focus on impact, not activities** + - ❌ "Held 12 customer interviews" + - ✅ "Identified #1 barrier to adoption (complexity of setup)" + +3. **Make problems visible early** + - Don't sugarcoat risks + - Propose solutions, not just problems + - Be specific about help needed + +4. **Use data to tell story** + - Quantify whenever possible + - Show trends, not just snapshots + - Connect metrics to business outcomes + +5. **Make it scannable** + - Use headers and bullet points + - Bold key information + - Use visual indicators (🟢🟡🔴, ↑→↓) + +## Status Guidelines + +**🟢 On Track**: Meeting all targets, no significant risks +**🟡 At Risk**: Potential issues that could impact delivery +**🔴 Blocked**: Critical issues preventing progress, needs intervention + +## Example Update + +``` +# Product Update: Customer Onboarding Redesign +**Week of Jan 20, 2026** + +## BLUF +**Status**: 🟡 At Risk +**Key Takeaway**: New onboarding flow is performing well in tests (+35% completion), but launch delayed one week due to integration issues with billing system. +**Action Needed**: Decision needed on whether to launch onboarding separately or wait for billing integration fix. + +## Progress Summary +- Completed user testing with 24 participants (94% positive feedback) +- Implemented first-time user experience improvements +- Resolved 12 of 15 bugs identified in QA + +## Key Metrics +| Metric | Current | Target | Trend | Status | +|--------|---------|--------|-------|--------| +| Onboarding Completion | 45% | 60% | → | 🟡 | +| Time to First Value | 4.2 min | 3.0 min | ↓ | 🟢 | +| Support Tickets (Setup) | 45/week | <30/week | ↓ | 🟢 | + +## Risks & Blockers +**HIGH: Billing System Integration Delay** +- **Impact**: Prevents users from completing onboarding flow +- **Root Cause**: API deprecation by payment processor, requires code rewrite +- **Mitigation**: Engineering team reallocated resources, fix ETA Feb 3 +- **Decision Needed**: Launch onboarding without payment integration or wait for fix? + +## Upcoming Milestones +**Next 30 Days:** +- Resolve billing integration (Feb 3) +- Launch onboarding redesign (Feb 5) +- Begin measuring impact on conversion (Feb 12) + +**Next 90 Days:** +- Iterate based on production data (March) +- Extend to mobile app (April) + +## Decision Needed +**Should we launch onboarding separately from billing integration?** + +**Option A: Launch Now (Recommended)** +- Pros: Get 35% completion rate improvement to users immediately, gather production data, maintain momentum +- Cons: Users need to complete payment in old flow, slightly disjointed experience + +**Option B: Wait for Billing Fix** +- Pros: Fully integrated experience from day one +- Cons: Delays benefits by 2 weeks, Q1 metric targets at risk + +**Recommendation**: Option A. The onboarding improvements are valuable independently, and the old payment flow works fine. Waiting risks missing Q1 targets. + +**Timeline**: Need decision by Jan 22 for Feb 5 launch. +``` +``` + +--- + +## Skill 4: Meeting Notes Template + +**File: `meeting-notes/SKILL.md`** + +```markdown +--- +name: meeting-notes +description: Structure and format meeting notes following PM best practices. Use when the user needs to create, format, or organize meeting notes, capture action items from meetings, or document discussions and decisions. +--- + +# Meeting Notes Skill + +This skill structures meeting notes to maximize value and ensure follow-through. + +## Standard Meeting Notes Template + +### Meeting Header +**Meeting**: [Meeting Title] +**Date**: [Date] +**Attendees**: [Names/Roles] +**Note Taker**: [Name] +**Duration**: [Actual duration] + +### Agenda +- [ ] Topic 1 +- [ ] Topic 2 +- [ ] Topic 3 + +*(Check off items as discussed)* + +### Decisions Made +Clear documentation of decisions: + +**Decision**: [What was decided] +**Context**: [Why this decision] +**Owner**: [Who's responsible for executing] +**Deadline**: [When if applicable] + +Use this format for each decision made. + +### Action Items +All action items should be: +- [ ] **[Action item]** - @Owner - Due: [Date] +- [ ] **[Action item]** - @Owner - Due: [Date] + +Format: +- Clear, specific action +- Single owner (no "team" ownership) +- Concrete deadline +- Checkbox for tracking + +### Discussion Notes +Key points discussed organized by topic: + +**Topic 1: [Name]** +- Key point or discussion highlight +- Important context or concern raised +- Any data or information shared + +**Topic 2: [Name]** +- Key discussion points + +### Open Questions / Follow-Up +Questions that couldn't be answered: +- **Question**: [What we need to know] +- **Owner**: [Who will find out] +- **By When**: [Deadline] + +### Next Steps +Clear summary of what happens next: +1. [Immediate next action] +2. [Follow-up meeting if needed] +3. [Any broader process to start] + +## Best Practices + +**During the meeting:** +- Focus on decisions and action items over dialogue +- Capture specific commitments, not generaldiscussion +- Note dissenting opinions on important decisions +- Ask for clarity on vague commitments ("I'll look into it" → "I'll analyze the data and share findings by Friday") + +**After the meeting:** +- Send notes within 2 hours while fresh +- Tag action item owners +- Include links to relevant documents +- Follow up on overdue action items + +**What to capture:** +✅ Decisions made +✅ Action items with owners and deadlines +✅ Key points of discussion +✅ Open questions +✅ Next steps + +**What to skip:** +❌ Verbatim transcripts +❌ Off-topic tangents +❌ Preliminary discussion before decisions +❌ Redundant information + +## Meeting Types & Adaptations + +### 1:1 Meetings +Focus on: +- Career development discussions +- Feedback (both directions) +- Current challenges +- Action items for both parties + +### Sprint Planning +Focus on: +- Story acceptance criteria +- Sizing/estimation decisions +- Dependency identification +- Sprint commitment + +### Product Reviews +Focus on: +- Design decisions +- User feedback discussed +- Changes requested +- Launch readiness assessment + +### Stakeholder Sync +Focus on: +- Status updates delivered +- Concerns raised +- Approvals given +- Escalation needs + +## Example Meeting Notes + +``` +# Product Roadmap Review - Q1 2026 +**Date**: January 20, 2026 +**Attendees**: Sarah (CPO), Mike (Eng Lead), Jennifer (Design), Tom (PM) +**Note Taker**: Tom +**Duration**: 45 minutes + +## Agenda +- [x] Review Q1 planned features +- [x] Discuss resource constraints +- [x] Prioritization discussion +- [x] Timeline alignment + +## Decisions Made + +**Decision**: Move multi-channel dashboard to Q2, prioritize mobile app improvements for Q1 +**Context**: Customer feedback shows mobile experience is significantly impacting retention (65% of users primarily mobile). Engineering team can only tackle one major initiative this quarter. +**Owner**: Tom (PM) to communicate to stakeholders +**Deadline**: January 22 + +**Decision**: Allocate 20% of engineering time to technical debt +**Context**: Accumulated tech debt is slowing feature development. Team velocity dropped 30% last quarter. +**Owner**: Mike (Eng Lead) to create tech debt backlog +**Deadline**: January 27 + +## Action Items +- [ ] **Update Q1 roadmap deck with new prioritization** - @Tom - Due: Jan 22 +- [ ] **Schedule alignment meeting with support team** - @Tom - Due: Jan 24 +- [ ] **Create tech debt prioritization rubric** - @Mike - Due: Jan 27 +- [ ] **Run user testing on mobile designs** - @Jennifer - Due: Feb 3 +- [ ] **Document decision rationale for executives** - @Sarah - Due: Jan 23 + +## Discussion Notes + +**Q1 Feature Prioritization** +- Customer retention is #1 company priority this quarter +- Mobile app NPS score is 6.2 (vs 8.1 for web) +- Mobile accounts for 65% of daily active users +- Multi-channel dashboard would take 8 engineering weeks +- Mobile improvements estimated at 6 engineering weeks with higher ROI + +**Resource Constraints** +- Currently 4 engineers available (down from 6 last quarter) +- Design team can support both initiatives but at reduced capacity +- QA team needs 2 weeks for thorough testing on mobile + +**Risk Discussion** +- Delaying dashboard may impact enterprise sales (3 deals waiting) +- Sarah noted: "We can position mobile improvements as foundation for enterprise features" +- Mike raised concern about mobile tech stack stability - addressed through tech debt allocation + +## Open Questions +- **Question**: What's the impact on enterprise pipeline if we delay dashboard? + **Owner**: Sarah will check with Sales + **By When**: January 23 + +- **Question**: Can we do a limited beta of dashboard for enterprise customers? + **Owner**: Tom will explore MVP scope + **By When**: January 25 + +## Next Steps +1. Tom to send updated roadmap to leadership by EOD Wednesday +2. Team to begin sprint planning for mobile improvements next Monday +3. Follow-up meeting on Feb 1 to review progress and validate prioritization +``` +``` + +I'll continue with Skills 5-7 in a separate file due to length... + diff --git a/pm-skills-examples-part2.md b/pm-skills-examples-part2.md new file mode 100644 index 0000000..14e74ed --- /dev/null +++ b/pm-skills-examples-part2.md @@ -0,0 +1,1043 @@ +# PM Claude Skills - Part 2 (Skills 5-7 + GitHub README) + +## Skill 5: Competitive Analysis + +**File: `competitive-analysis/SKILL.md`** + +```markdown +--- +name: competitive-analysis +description: Analyze competitors and create competitive landscape documentation. Use when the user asks to analyze competitors, create competitive analysis, compare features with competitors, track competitive landscape, or understand competitive positioning. +--- + +# Competitive Analysis Skill + +This skill creates structured competitive analyses for product decision-making. + +## Analysis Framework + +### 1. Executive Summary +- **Market Position**: Where we stand relative to competitors +- **Key Findings**: Top 3-5 insights from analysis +- **Strategic Implications**: What this means for our roadmap + +### 2. Competitor Profiles + +For each major competitor: + +**[Competitor Name]** +- **Company Overview**: Size, funding, market position +- **Target Customer**: Who they serve +- **Value Proposition**: Their core positioning +- **Business Model**: How they make money +- **Strengths**: What they do well +- **Weaknesses**: Where they fall short +- **Recent Activity**: Major updates, funding, announcements + +### 3. Feature Comparison Matrix + +| Feature | Us | Competitor A | Competitor B | Competitor C | +|---------|-----|--------------|--------------|--------------| +| Core Feature 1 | ✅ Full | ✅ Full | ⚠️ Limited | ❌ None | +| Core Feature 2 | ✅ Full | ⚠️ Limited | ✅ Full | ✅ Full | +| Advanced Feature 1 | ⚠️ Beta | ❌ None | ✅ Full | ❌ None | + +Legend: +- ✅ Full: Complete, production-ready feature +- ⚠️ Limited/Beta: Partial or in-development +- ❌ None: Feature not available + +Include notes on quality/implementation differences where significant. + +### 4. Pricing Comparison + +| Plan Type | Us | Competitor A | Competitor B | Competitor C | +|-----------|-----|--------------|--------------|--------------| +| Free/Trial | $0 | $0 | $0 | N/A | +| Starter | $29/mo | $25/mo | $39/mo | $49/mo | +| Professional | $79/mo | $89/mo | $79/mo | $99/mo | +| Enterprise | Custom | Custom | $299/mo | Custom | + +**Pricing Strategy Notes**: +- How our pricing compares +- Value perception +- Packaging differences + +### 5. Strengths & Weaknesses Analysis + +**Our Competitive Advantages:** +1. [Strength] - [Why it matters] +2. [Strength] - [Why it matters] +3. [Strength] - [Why it matters] + +**Our Gaps vs. Competition:** +1. [Gap] - [Impact on customers] +2. [Gap] - [Impact on customers] +3. [Gap] - [Impact on customers] + +### 6. Customer Perception Analysis + +**What Customers Say About Competitors** (from reviews, G2, social media): + +**Competitor A:** +- Most Praised: [Common positive feedback] +- Most Criticized: [Common complaints] +- Typical User: [Who uses them] + +**Competitor B:** +- Most Praised: [Common positive feedback] +- Most Criticized: [Common complaints] +- Typical User: [Who uses them] + +### 7. Market Positioning Map + +Describe or diagram positioning on key dimensions: +- Y-Axis: [e.g., Enterprise vs. SMB] +- X-Axis: [e.g., Simple vs. Comprehensive] + +**Our Position**: [Where we sit and why] +**Whitespace Opportunities**: [Underserved segments] + +### 8. Win/Loss Analysis + +**Why We Win Against Competitors:** +- Better at: [Specific capabilities] +- Target customers that value: [What matters] + +**Why We Lose to Competitors:** +- When customers need: [Specific requirements] +- When they prioritize: [What they value] + +### 9. Strategic Implications & Recommendations + +**Immediate Actions** (0-3 months): +1. [Action] - [Rationale] +2. [Action] - [Rationale] + +**Medium-term Strategy** (3-12 months): +1. [Action] - [Rationale] +2. [Action] - [Rationale] + +**Long-term Positioning** (12+ months): +1. [Strategic direction] - [Rationale] + +## Analysis Best Practices + +**Data Sources:** +- Competitor websites and documentation +- G2, Capterra, TrustRadius reviews +- Customer interviews (especially win/loss) +- Sales team feedback +- Social media and community discussions +- Industry analysts and reports +- Competitor job postings (reveal strategy) + +**Quality Standards:** +✅ Use recent data (within 3-6 months) +✅ Include sources for claims +✅ Focus on verifiable facts over assumptions +✅ Consider different customer segments +✅ Update regularly (at least quarterly) + +❌ Don't rely solely on competitor marketing +❌ Don't ignore smaller/emerging competitors +❌ Don't assume features work well just because they exist +❌ Don't forget about indirect/substitute competitors + +**Ethical Guidelines:** +- Use only publicly available information +- Don't misrepresent competitor capabilities +- Be honest about their strengths +- Don't disparage competitors personally + +## Monitoring Cadence + +**Weekly**: Check for major announcements, funding, leadership changes +**Monthly**: Review feature releases, pricing changes, marketing campaigns +**Quarterly**: Comprehensive feature comparison, strategic assessment +**Annually**: Market position analysis, long-term trend evaluation + +## Example Analysis Section + +``` +## Competitor Profile: DataSync Pro + +**Company Overview** +- Founded 2019, 85 employees, $12M Series A (2023) +- Fast-growing in mid-market segment +- Strong presence in Europe + +**Target Customer** +- Mid-market companies (100-1000 employees) +- Technical users comfortable with APIs +- Data-intensive operations + +**Value Proposition** +"The fastest way to sync data across your entire stack" +- Focus on speed and reliability +- Developer-first approach + +**Business Model** +- Freemium with generous free tier +- Usage-based pricing above free limits +- Professional services for enterprise + +**Strengths** +- Superior sync speed (2-3x faster than alternatives) +- Best-in-class developer documentation +- Strong developer community (5k+ GitHub stars) +- Excellent uptime (99.97% vs industry 99.5%) +- Modern, intuitive API design + +**Weaknesses** +- Limited no-code options (requires technical knowledge) +- Smaller integration library (45 vs our 120) +- No dedicated enterprise features +- Limited customization options +- Support can be slow (avg 8hr response time) + +**Recent Activity** +- Jan 2026: Released real-time sync capabilities +- Dec 2025: Raised $12M Series A +- Nov 2025: Added webhooks and event streaming +- Hired ex-Stripe engineering lead as CTO + +**Strategic Implications** +- Their focus on speed creates pressure on our performance +- Developer-first approach winning technical buyers +- Gaps in no-code and enterprise create opportunities +- Need to monitor their enterprise moves closely +``` +``` + +--- + +## Skill 6: Data Analysis Standard + +**File: `data-analysis-standard/SKILL.md`** + +```markdown +--- +name: data-analysis-standard +description: Analyze data and metrics following PM analysis frameworks. Use when the user provides data, metrics, analytics, experiment results, A/B test results, or asks for data analysis, metric interpretation, or statistical analysis. +--- + +# Data Analysis Standard Skill + +This skill provides a structured approach to analyzing product metrics and experimental data. + +## Analysis Framework + +### 1. Context Setting +- **Question**: What are we trying to understand? +- **Hypothesis**: What we expected to find +- **Data Source**: Where the data comes from +- **Time Period**: Date range analyzed +- **Sample Size**: Number of observations + +### 2. Data Summary +- **Key Metrics**: Primary measurements +- **Segments Analyzed**: How data was broken down +- **Data Quality Notes**: Any issues or limitations + +### 3. Findings + +**Primary Finding** +- **Observation**: What the data shows +- **Magnitude**: Size of effect (with units) +- **Significance**: Statistical significance if applicable +- **Confidence**: How certain we are + +**Secondary Findings** +- List additional insights +- Note unexpected patterns +- Highlight anomalies + +### 4. Segment Analysis + +Break down by relevant dimensions: +- User type/persona +- Time period (trends) +- Geographic region +- Platform/device +- User cohort + +### 5. Statistical Rigor + +**For A/B Tests:** +- Sample size per variant +- Test duration +- Statistical significance (p-value) +- Confidence interval +- Statistical power +- Minimum detectable effect + +**Statistical Significance Thresholds:** +- p < 0.05: Statistically significant +- p < 0.01: Highly significant +- p >= 0.05: Not significant (don't ship) + +**Minimum Sample Size:** +- At least 1000 users per variant +- At least 100 conversions per variant +- Run for minimum 1 full week (capture weekly patterns) + +### 6. Interpretation & Implications + +**What This Means:** +- Business impact translation +- Product implications +- Strategic relevance + +**What This Doesn't Mean:** +- Common misinterpretations to avoid +- Correlation vs. causation notes +- Scope limitations + +### 7. Recommendations + +**Recommended Action:** +- Clear next step +- Supporting rationale +- Risk assessment + +**Alternative Considerations:** +- Other options +- Trade-offs +- Further validation needed + +### 8. Follow-Up Questions + +What we still need to learn: +- Additional analysis needed +- New experiments to run +- Data gaps to fill + +## Analysis Best Practices + +**Statistical Guidelines:** + +1. **Always check for statistical significance** + - Don't call results based on direction alone + - Report both p-value and confidence intervals + - Account for multiple comparisons + +2. **Consider practical significance** + - A 0.1% improvement might be statistically significant but not meaningful + - Consider business impact, not just p-values + - Factor in implementation cost + +3. **Watch for common pitfalls:** + - Selection bias in sample + - Simpson's paradox in segments + - Regression to the mean + - Novelty effects in experiments + - Seasonal patterns + +4. **Validate data quality:** + - Check for tracking issues + - Verify sample sizes are adequate + - Look for data anomalies + - Confirm proper randomization + +**Communication Guidelines:** + +✅ **Do:** +- Lead with the answer +- Quantify everything possible +- Show your work (methodology) +- Acknowledge limitations +- Provide context for numbers + +❌ **Don't:** +- Hide negative results +- Cherry-pick favorable data +- Overstate confidence +- Use jargon without explanation +- Confuse correlation with causation + +## Metrics Definitions + +**Engagement Metrics:** +- **DAU**: Daily Active Users (users who performed key action today) +- **WAU**: Weekly Active Users (users who performed key action in last 7 days) +- **MAU**: Monthly Active Users (users who performed key action in last 30 days) +- **Stickiness**: DAU/MAU ratio (higher = more frequent usage) + +**Retention Metrics:** +- **D1 Retention**: % of users who return 1 day after signup +- **D7 Retention**: % of users who return 7 days after signup +- **D30 Retention**: % of users who return 30 days after signup + +**Conversion Metrics:** +- **Conversion Rate**: % of users who complete desired action +- **Funnel Drop-off**: % lost at each step +- **Time to Convert**: How long users take to convert + +**Good Benchmark Ranges** (vary by industry): +- D1 Retention: 40-60% +- D7 Retention: 20-40% +- D30 Retention: 10-25% +- Conversion Rate: 2-5% (freemium SaaS) + +## Example Analysis + +``` +# A/B Test Analysis: Onboarding Flow Redesign + +## Context +**Question**: Does the new onboarding flow improve activation rates? +**Hypothesis**: New flow will increase activation by 20% by reducing friction +**Data Source**: Mixpanel event tracking +**Time Period**: Jan 1-14, 2026 (14 days) +**Sample Size**: 5,240 users (2,620 per variant) + +## Data Summary +**Key Metric**: Activation rate (completed setup + first key action) +**Segments**: New users, mobile vs desktop, organic vs paid + +**Data Quality**: +- No tracking issues detected +- Balanced randomization (50.1% / 49.9%) +- Sample sizes exceed minimum thresholds + +## Findings + +**Primary Finding** +**Observation**: New onboarding flow increased activation rate from 45.2% to 52.8% +**Magnitude**: +7.6 percentage points (+16.8% relative improvement) +**Significance**: p = 0.003 (highly significant) +**Confidence**: 95% CI: [+4.2pp, +11.0pp] + +✅ **Recommendation**: Ship new onboarding flow + +**Secondary Findings**: +- Mobile users showed larger improvement (+22%) than desktop (+12%) +- Effect consistent across organic and paid users +- Time to activation reduced from 8.2min to 5.7min (-30%) +- Support tickets about setup decreased by 35% + +## Segment Analysis + +| Segment | Control | Treatment | Lift | Significance | +|---------|---------|-----------|------|--------------| +| Overall | 45.2% | 52.8% | +16.8% | p = 0.003 ** | +| Mobile | 41.0% | 50.0% | +22.0% | p = 0.008 ** | +| Desktop | 49.4% | 55.2% | +11.7% | p = 0.042 * | +| Organic | 46.8% | 53.5% | +14.3% | p = 0.019 * | +| Paid | 43.1% | 51.8% | +20.2% | p = 0.012 * | + +* p < 0.05, ** p < 0.01 + +**Key Insight**: Improvement is consistent across all segments, suggesting robust effect. + +## Statistical Rigor +- ✅ Sample size: 2,620 per variant (exceeds 1,000 minimum) +- ✅ Conversions: 1,184 and 1,383 (exceeds 100 minimum) +- ✅ Duration: 14 days (captures two full weeks) +- ✅ Statistical power: 92% (exceeds 80% target) +- ✅ Minimum detectable effect: 5pp (we detected 7.6pp) + +## Interpretation & Implications + +**What This Means**: +- New onboarding reliably improves activation +- For every 100 new users, we'll activate ~8 more +- At current signup rate (500/day), that's ~40 additional activated users per day +- Projected impact: +1,200 activated users per month + +**What This Doesn't Mean**: +- We don't know long-term retention impact yet (need 30-day follow-up) +- This doesn't tell us which specific changes drove the improvement +- Results may diminish slightly post-novelty period (monitor for 30 days) + +## Recommendations + +**Recommended Action**: Ship new onboarding flow to 100% of users +- Strong, statistically significant improvement +- Consistent across segments +- No negative signals +- Technical implementation is stable + +**Rollout Plan**: +- Week 1: Deploy to 100% (already tested at scale) +- Week 2-5: Monitor retention metrics closely +- Month 2: Measure long-term impact on retention and LTV + +**Monitor These Metrics**: +- D7 and D30 retention (ensure activation translates to retention) +- Support ticket volume (should remain low) +- NPS scores (ensure quality of experience) + +## Follow-Up Questions + +**Additional Analysis Needed**: +- Which specific onboarding changes had biggest impact? (follow-up multivariate test) +- Does improved activation lead to better long-term retention? (cohort analysis in 30 days) +- Can we further optimize mobile experience given larger effect? (mobile-specific test) + +**Next Experiments**: +- Test additional friction reduction in mobile flow +- Experiment with personalized onboarding paths +- A/B test welcome email timing and content +``` +``` + +--- + +## Skill 7: Roadmap Presentation + +**File: `roadmap-presentation/SKILL.md`** + +```markdown +--- +name: roadmap-presentation +description: Create product roadmap presentations for stakeholders. Use when the user asks to create a roadmap, roadmap presentation, product roadmap, quarterly plan, strategic roadmap, or needs to visualize product plans and timelines. +--- + +# Roadmap Presentation Skill + +This skill creates effective product roadmap presentations that communicate strategy and build stakeholder alignment. + +## Presentation Structure + +### Slide 1: Title & Context +**Product Roadmap - [Time Period]** +- Product/Team name +- Time period covered +- Last updated date +- Your name and role + +### Slide 2: Executive Summary +**TL;DR for busy executives:** +- **Strategic Focus**: One sentence on the theme/priority +- **Key Initiatives**: 3-5 major efforts +- **Expected Outcomes**: Top metrics we'll move +- **Resource Requirements**: Team size, budget, dependencies + +### Slide 3: Strategic Context +**Why This Roadmap?** +- **Company Objectives**: How this aligns with company goals +- **Market Context**: Relevant competitive or market dynamics +- **Customer Needs**: Top problems we're solving +- **Success Metrics**: How we'll measure progress + +### Slide 4: Roadmap Principles +**How We Prioritize:** +- [Principle 1]: e.g., "Customer retention over acquisition" +- [Principle 2]: e.g., "Technical foundation before features" +- [Principle 3]: e.g., "Enterprise needs vs. broad market" + +These help stakeholders understand trade-offs. + +### Slides 5-7: Timeline View + +**Now (Month 1-2)** - What's actively being built +- Initiative 1: [Name] + - Problem solved + - Expected impact + - Team/effort + +- Initiative 2: [Name] + - Problem solved + - Expected impact + - Team/effort + +**Next (Month 3-4)** - What's coming soon +- Initiative 3: [Name] + - Problem solved + - Expected impact + - Team/effort + +**Later (Month 5-6)** - What's on the horizon +- Initiative 4: [Name] + - Problem solved + - Expected impact + - Team/effort + +### Slide 8: Feature Details (if needed) +Deep dive on 1-2 key initiatives: +- **Problem**: What customer pain we're solving +- **Solution**: What we're building +- **Impact**: Expected business outcomes +- **Effort**: Team and timeline +- **Dependencies**: What needs to happen first + +### Slide 9: What We're NOT Doing +**Important to set expectations:** +- Feature X: [Why not now] +- Feature Y: [Why not now] +- Feature Z: [Why not now] + +Shows you've considered requests and made deliberate choices. + +### Slide 10: Risks & Dependencies +**What Could Go Wrong:** +- **Risk 1**: [Description] - [Mitigation] +- **Risk 2**: [Description] - [Mitigation] + +**External Dependencies:** +- Dependency on team X for Y +- Waiting on decision Z +- Partnership with vendor W + +### Slide 11: Success Metrics +**How We'll Know We Succeeded:** + +| Metric | Current | Q-End Target | Long-term Goal | +|--------|---------|--------------|----------------| +| [Key Metric 1] | [Value] | [Target] | [Goal] | +| [Key Metric 2] | [Value] | [Target] | [Goal] | +| [Key Metric 3] | [Value] | [Target] | [Goal] | + +### Slide 12: Team & Resources +**What We Need to Deliver:** +- Engineering: [X engineers + roles] +- Design: [X designers + focus areas] +- PM: [X PMs + responsibilities] +- Other: [Data, QA, DevOps needs] + +**Open Positions** (if applicable) +**Budget Requirements** (if applicable) + +### Slide 13: Q&A +Leave blank for discussion + +## Visual Design Guidelines + +**Layout:** +- Use consistent colors for different initiative types +- Now/Next/Later should have clear visual distinction +- Use icons for different feature categories +- Keep text minimal - speak to slides, don't read them + +**Color Coding Examples:** +- 🟦 Foundation/Platform work +- 🟩 Customer-facing features +- 🟨 Technical debt/quality +- 🟥 Security/compliance +- 🟪 Experimental/R&D + +**Timeline Visualization:** +Use Gantt-style bars or swim lanes: +``` +Jan Feb Mar Apr May Jun +[====== Initiative 1 ======] + [===== Initiative 2 =====] + [===== Initiative 3 =====] +``` + +## Roadmap Communication Principles + +**1. Outcomes Over Features** +- ❌ "Build multi-channel dashboard" +- ✅ "Enable support teams to respond 3x faster to customer inquiries" + +**2. Show Trade-offs** +- Explain what you're not doing and why +- Make prioritization framework explicit +- Acknowledge competing requests + +**3. Manage Expectations** +- Use "Now/Next/Later" not specific dates (dates create false precision) +- Show confidence levels (High/Medium/Low) +- Be honest about risks + +**4. Tell a Story** +- Connect initiatives to strategy +- Show how pieces build on each other +- Explain the arc from now to vision + +**5. Make it Actionable** +- Clear on what you need from stakeholders +- Specific decision points +- Defined success criteria + +## Roadmap Formats + +### Theme-Based Roadmap +Organize by strategic themes rather than time: +- **Theme 1: Improve Onboarding** + - Initiative A + - Initiative B +- **Theme 2: Scale for Enterprise** + - Initiative C + - Initiative D + +Good for: Communicating strategy, longer time horizons + +### Timeline Roadmap +Organize by time periods: +- Q1 2026 +- Q2 2026 +- H2 2026 + +Good for: Execution planning, near-term clarity + +### Now/Next/Later Roadmap (Recommended) +Three buckets without specific dates: +- **Now**: In progress (0-2 months) +- **Next**: Up next (2-4 months) +- **Later**: On the horizon (4-12 months) + +Good for: Managing expectations, reducing date commitments + +### Outcome-Based Roadmap +Organize by business outcomes: +- **Increase Retention**: Initiatives that reduce churn +- **Drive Expansion**: Initiatives that increase ARPU +- **Improve Efficiency**: Initiatives that reduce costs + +Good for: Executive audiences, strategic alignment + +## Stakeholder-Specific Adaptations + +### For Executives +- Focus on outcomes and metrics +- Show strategic alignment +- Be brief and high-level +- Emphasize business impact + +### For Engineering +- Include technical details +- Show architecture implications +- Discuss technical debt trade-offs +- Be specific about scope + +### For Sales/CS +- Focus on customer benefits +- Include competitive positioning +- Show launch timeline +- Provide messaging guidance + +### For Customers/Partners +- External-safe language +- Focus on value, not internals +- Broad time ranges +- Beautiful design (represents brand) + +## Example Slide Content + +``` +# Product Roadmap - Q1 2026 +Customer Success Platform +Last Updated: January 15, 2026 +Sarah Chen, Senior Product Manager + +--- + +## Executive Summary + +**Strategic Focus**: Accelerate customer onboarding and reduce time-to-value + +**Key Initiatives**: +1. Redesigned onboarding flow (expected +20% activation) +2. In-app guidance system (expected -40% support tickets) +3. Mobile app improvements (expected +15% engagement) + +**Expected Outcomes**: +- Activation rate: 45% → 60% +- Time to first value: 12 days → 5 days +- Day 30 retention: 68% → 75% + +**Resource Requirements**: 4 engineers, 1 designer, full quarter + +--- + +## Strategic Context + +**Company Objectives**: +- Improve net revenue retention from 95% to 105% +- Reduce CAC payback from 18 months to 12 months + +**Market Context**: +- 3 competitors launched improved onboarding in 2025 +- Customer expectations for SaaS onboarding have evolved +- 62% of churned customers never completed onboarding + +**Customer Needs**: +- "Too complicated to get started" (top churn reason) +- "Don't know how to use advanced features" +- "Mobile experience is frustrating" + +**Success Metrics**: +- Activation rate (completed setup + first action) +- Time to first value +- Day 30 retention rate + +--- + +## Now (January - February) + +### 🟩 Onboarding Redesign - "Fast Start" +**Problem**: 55% of new users don't complete onboarding, leading to poor activation and eventual churn. + +**Solution**: Streamlined 3-step onboarding with progressive disclosure of advanced features. Users can start using core functionality in <5 minutes. + +**Expected Impact**: +- Activation rate: 45% → 60% (+33%) +- Support tickets: -40% +- Time to value: 12 days → 5 days + +**Effort**: 6 engineering weeks, 3 design weeks + +**Timeline**: Design complete Jan 15, Development Jan 22-Feb 12, Launch Feb 19 + +--- + +## Next (March - April) + +### 🟩 In-App Guidance System +**Problem**: Users don't discover advanced features, limiting expansion revenue. 80% of users never use more than 3 features. + +**Solution**: Contextual tooltips, feature tours, and achievement system that guides users to discover relevant capabilities based on their use case. + +**Expected Impact**: +- Feature adoption: +45% +- Expansion revenue: +15% +- NPS: 42 → 50 + +**Effort**: 8 engineering weeks, 2 design weeks + +**Dependencies**: Requires onboarding redesign to complete first + +--- + +## Later (May - June) + +### 🟩 Mobile App V2 +**Problem**: Mobile experience is subpar, driving users back to desktop and reducing engagement. + +**Solution**: Rebuilt mobile app with improved performance, offline support, and streamlined workflows for key mobile use cases. + +**Expected Impact**: +- Mobile DAU: +60% +- Overall DAU: +15% +- Mobile NPS: 32 → 45 + +**Effort**: 10 engineering weeks, 4 design weeks + +--- + +## What We're NOT Doing (This Quarter) + +**Multi-Channel Dashboard** +- Why not now: Onboarding and retention are higher priorities; only requested by 8% of customers +- When: Q2 2026 after retention improvements ship + +**Advanced Reporting** +- Why not now: Need to improve core experience first; only valuable for activated users +- When: H2 2026 once activation targets are met + +**Desktop App** +- Why not now: Focus on web and mobile; small portion of customers (12%) requesting this +- When: 2027 consideration based on demand + +--- + +## Risks & Mitigation + +**Risk: Onboarding redesign doesn't improve activation** +- Mitigation: Extensive user testing (completed), beta launch to 20% before full rollout, kill switch ready + +**Risk: Mobile rebuild takes longer than estimated** +- Mitigation: Using modern framework we have experience with, dedicated team, parallel track to avoid dependencies + +**Risk: Engineering velocity impacted by production issues** +- Mitigation: Allocated 20% time for tech debt and stability, on-call rotation protects focus time + +--- + +## Success Metrics - Q1 Targets + +| Metric | Current (Jan) | Q1 Target | Long-term Goal | +|--------|---------------|-----------|----------------| +| Activation Rate | 45% | 60% | 70% | +| Time to First Value | 12 days | 5 days | 1 day | +| Day 30 Retention | 68% | 75% | 85% | +| Setup Support Tickets | 180/week | 100/week | 50/week | +| Feature Adoption | 2.8/user | 4.0/user | 6.0/user | + +**Measurement**: Weekly tracking, monthly reviews with stakeholders + +--- + +## Team & Resources + +**Current Team**: +- 4 Engineers (2 frontend, 1 backend, 1 full-stack) +- 1 Product Designer +- 1 Product Manager +- QA support from shared team + +**What We Need**: +- ✅ Current team sufficient for Q1 roadmap +- ⚠️ Mobile rebuild may require additional frontend eng in Q2 +- ⚠️ Design support will be tight with 3 parallel initiatives + +**No budget increases required this quarter** +``` +``` + +--- + +## Sample GitHub README.md + +```markdown +# Product Management Claude Skills + +**Transform your PM workflow with specialized Claude Skills for common product management tasks.** + +[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) +[![GitHub stars](https://img.shields.io/github/stars/yourusername/pm-claude-skills.svg)](https://github.com/yourusername/pm-claude-skills/stargazers) + +> 📖 **Background**: These Skills emerged from my widely-read Medium article ["Claude Skills: The AI Feature That's Quietly Changing How Product Managers Work"](link-to-article), where I documented how Skills transformed my daily PM workflow, saving 3-4 hours per week. + +## What Are These Skills? + +Claude Skills are reusable, specialized procedures that teach Claude your exact workflows. Instead of re-explaining your PRD format or meeting notes structure every time, you create a Skill once and Claude automatically applies it whenever relevant. + +Think of Skills as "onboarding guides" for Claude—they package your best practices, templates, and processes so Claude consistently delivers outputs the way you want them. + +## 🎯 Who Is This For? + +- **Product Managers** looking to automate repetitive documentation tasks +- **PM Teams** wanting to standardize processes and share best practices +- **Anyone** tired of reformatting Claude's outputs to match their standards + +## ⚡ Quick Start (5 Minutes) + +1. **Prerequisites**: You need Claude Pro, Max, Team, or Enterprise account +2. **Enable Code Execution**: Settings → Features → Enable "Code Execution and File Creation" +3. **Install Your First Skill**: + ``` + 1. Download: [`prd-template.skill`](link) + 2. Go to claude.ai + 3. Settings → Skills → Upload Skill + 4. Try it: "Help me write a PRD for a mobile app onboarding feature" + ``` + +That's it! Claude now knows your PRD format. + +## 📦 Available Skills + +### Free Essential Skills (Included) + +| Skill | Purpose | Time Saved | Skill File | +|-------|---------|------------|------------| +| **PRD Template** | Standardized product requirements | 2-3 hrs/PRD | [Download](link) | +| **Meeting Notes** | Structured meeting documentation | 15-30 min/meeting | [Download](link) | +| **Stakeholder Update** | Executive status updates | 30-45 min/update | [Download](link) | +| **User Research Synthesis** | Analyze and synthesize research findings | 2-3 hrs/research study | [Download](link) | +| **Competitive Analysis** | Structured competitive assessments | 1-2 hrs/analysis | [Download](link) | + +### Premium Skills Library ($49 one-time) 🔓 + +Get the complete collection of 15+ Skills including: + +- **Advanced Planning**: Quarterly Planning, Product Launch Checklist, OKR Framework +- **Specialized Docs**: Technical Specification, Go-to-Market Plan, Feature Brief +- **Data & Analytics**: A/B Test Analysis, Metric Deep-Dive, User Segmentation +- **Communication**: Sales Enablement, Customer FAQ, Release Notes +- **Team Skills**: Sprint Planning, Retrospective, 1:1 Agenda + +[**→ Get Premium Skills**](your-gumroad-link) + +All premium Skills include lifetime updates and support. + +## 💡 Real Results + +> "These Skills have become indispensable. I used to spend 3-4 hours every Friday on stakeholder updates. Now it takes 20 minutes to compile everything and let Claude format it. Game-changer." +> — **Mohit Aggarwal, Senior PM** + +**Time savings per week:** +- PRD creation: -2.5 hours +- Meeting notes: -1.5 hours +- Stakeholder updates: -2.0 hours +- Research synthesis: -2.5 hours +- **Total: ~8-9 hours/week back in your schedule** + +## 📚 Documentation + +- [Installation Guide](docs/installation.md) - Step-by-step setup +- [Customization Guide](docs/customization.md) - Adapt Skills to your workflow +- [Skill Creation Tutorial](docs/skill-creation-tutorial.md) - Build your own Skills +- [Troubleshooting](docs/troubleshooting.md) - Common issues and fixes + +## 🤝 Contributing + +Found a bug? Want to suggest an improvement? Contributions are welcome! + +- [Report an Issue](github-issues-link) +- [Submit a Pull Request](github-pr-link) +- [Join Discussions](github-discussions-link) + +See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. + +## ⭐ Show Your Support + +If these Skills save you time, please: +1. ⭐ Star this repository +2. 📢 Share with fellow PMs +3. 🐛 Report bugs or suggest improvements +4. ✍️ Write about your experience + +## 📈 Roadmap + +**Coming Soon:** +- Domain-specific Skills (SaaS PM, B2B PM, Growth PM) +- Video tutorials for each Skill +- Notion/Confluence template packs +- Team collaboration Skills + +**Long-term:** +- Interactive Skill builder tool +- Integration with PM tools (Jira, Productboard, etc.) +- Community-contributed Skills library + +## 📄 License + +This project is licensed under the MIT License - see [LICENSE](LICENSE) for details. + +You're free to use, modify, and distribute these Skills. Attribution appreciated but not required. + +## 🙋 FAQ + +**Q: Do I need a paid Claude account?** +A: Yes, Skills require Claude Pro, Max, Team, or Enterprise. + +**Q: Can I customize these Skills for my team?** +A: Absolutely! See our [Customization Guide](docs/customization.md). + +**Q: Do Skills work with the Claude API?** +A: Yes! Skills work in claude.ai, Claude Code, and via the API. + +**Q: What if I need help with a specific use case?** +A: Open a [Discussion](github-discussions-link) or check out my [consulting services](link). + +**Q: Are you building Skills for other roles?** +A: Currently focused on PM Skills, but open to expanding. Let me know what you'd like to see! + +## 💼 Professional Services + +Need custom Skills for your team? I offer: +- Custom Skill development ($500-2000 per Skill) +- Team workshops and training ($2000-5000) +- PM process consulting +- [Contact me](mailto:your-email) to discuss your needs + +## 🔗 Links + +- 📝 [Original Medium Article](link-to-article) +- 🐦 [Follow me on Twitter](twitter-link) +- 💼 [Connect on LinkedIn](linkedin-link) +- ✉️ [Email me](mailto:your-email) + +--- + +**Made with ☕ by [Mohit Aggarwal](your-website)** + +*Helping product managers work smarter with AI* + +⭐ Star this repo to get updates as new Skills are added! +```