justin/pm-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: sync all skill updates and new skills into plugin bundles

Browse Source 
- Synced 97 existing skill SKILL.md files from skills/ to their plugin bundle copies
- Added 7 new skills to plugin bundles:
  - seo-content-brief, media-pitch -> pm-gtm
  - tax-planning-checklist -> pm-finance
  - change-management-plan -> pm-hr
  - sales-forecasting-model -> pm-sales
  - workshop-facilitation-guide -> pm-operations
  - teaching-lesson-plan -> pm-cross

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
mohitagw15856
2026-04-20 21:00:00 +01:00
parent d7f6c2cd05
commit 513e1d3ce7
67 changed files with 1851 additions and 507 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/pm-essentials/skills/competitive-analysis/SKILL.md
+53 -211
View File
@@ -1,251 +1,93 @@
---
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.
description: "Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations."
---
# Competitive Analysis Skill
This skill creates structured competitive analyses for product decision-making.
Create structured competitive analyses for product decision-making.
## Analysis Framework
## Required Inputs
Ask the user for these if not provided:
- **Your product or company** (what you're comparing against)
- **Competitors to analyze** (or ask to identify the top 3-5)
- **Analysis focus** (full landscape / feature comparison / pricing / positioning / win-loss)
- **Audience** (product team / leadership / sales / board)
## Process
1. Gather competitor information from provided inputs and available context
2. Build profiles for each competitor
3. Create feature comparison matrix on dimensions that matter to the user's customers
4. Analyze pricing and positioning
5. Identify win/loss patterns and strategic implications
6. **Validate** — Confirm all claims reference a specific source or are flagged as assumptions. Verify feature comparisons note quality differences, not just presence/absence.
## Output Structure
### 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
- **Key Findings**: Top 3-5 insights
- **Strategic Implications**: What this means for the roadmap
### 2. Competitor Profiles
For each major competitor:
**[Competitor Name]**
For each competitor:
- **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
- **Value Proposition**: Core positioning
- **Strengths / Weaknesses**: What they do well and 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 |
| [Feature] | ✅ Full | ⚠️ Limited | ❌ None | ✅ Full |
Legend:
- ✅ Full: Complete, production-ready feature
- ⚠️ Limited/Beta: Partial or in-development
- ❌ None: Feature not available
Legend: ✅ Full (production-ready) · ⚠️ Limited/Beta · ❌ None
Include notes on quality/implementation differences where significant.
Include notes on quality and 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 |
| Plan | Us | Competitor A | Competitor B |
|------|-----|--------------|--------------|
| Free/Trial | [price] | [price] | [price] |
| Pro | [price] | [price] | [price] |
| Enterprise | [price] | [price] | [price] |
**Pricing Strategy Notes**:
- How our pricing compares
- Value perception
- Packaging differences
### 5. Market Positioning Map
### 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:
Position competitors on two key dimensions relevant to the market:
- 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
### 6. Win/Loss Analysis
**Why We Win Against Competitors:**
- Better at: [Specific capabilities]
- Target customers that value: [What matters]
**Why We Win:**
- Better at: [specific capabilities]
- Customers who value: [what matters to them]
**Why We Lose to Competitors:**
- When customers need: [Specific requirements]
- When they prioritize: [What they value]
**Why We Lose:**
- When customers need: [specific requirements]
- Their advantage: [what tips the decision]
### 9. Strategic Implications & Recommendations
### 7. Strategic Recommendations
**Immediate Actions** (0-3 months):
1. [Action] - [Rationale]
2. [Action] - [Rationale]
**Immediate Actions (0-3 months):**
1. [Action] — [Rationale]
**Medium-term Strategy** (3-12 months):
1. [Action] - [Rationale]
2. [Action] - [Rationale]
**Medium-term (3-12 months):**
1. [Action] — [Rationale]
**Long-term Positioning** (12+ months):
1. [Strategic direction] - [Rationale]
## Quality Checks
## 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
```
## Feature Comparison Best Practices
When comparing features:
1. **Group by Category**
- Core functionality
- Integration capabilities
- Analytics/reporting
- Security/compliance
- Collaboration features
2. **Note Quality Differences**
- Not all implementations are equal
- Speed, reliability, UX matter
- Example: "Both have API, but theirs has rate limits"
3. **Consider the Complete Experience**
- Onboarding process
- Documentation quality
- Support responsiveness
- Mobile experience
4. **Identify Gaps That Matter**
- What customers actually care about
- Not just feature count
- Focus on differentiators
## Win/Loss Analysis Template
When analyzing why you win or lose deals:
**Win Against [Competitor]**
- **Scenarios**: When do we win?
- **Key Differentiators**: What tips the decision?
- **Customer Quotes**: What they tell us
- **Typical Profile**: Who chooses us?
**Loss Against [Competitor]**
- **Scenarios**: When do we lose?
- **Their Advantages**: What tips the decision?
- **Customer Quotes**: What they tell us
- **Typical Profile**: Who chooses them?
**Lessons Learned**
- What we need to improve
- What we need to communicate better
- Where we should compete differently
- [ ] All competitor claims cite a source or are flagged as assumptions
- [ ] Feature comparison notes quality differences, not just feature presence
- [ ] Strategic recommendations are specific actions, not generic advice
- [ ] Win/loss analysis reflects customer perspective, not internal assumptions
- [ ] Different customer segments are considered (not all buyers value the same things)
plugins/pm-essentials/skills/meeting-notes/SKILL.md
+9 -1
View File
@@ -1,6 +1,6 @@
---
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.
description: "Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps."
---
# Meeting Notes Skill
@@ -243,6 +243,14 @@ Template additions:
**Notes Sent**: January 20, 2026 5:30 PM
```
## Quality Checks
- [ ] Every action item has a single named owner (not "team")
- [ ] Every action item has a concrete deadline
- [ ] Decisions include context (why the decision was made)
- [ ] Open questions have an owner and a "by when"
- [ ] No verbatim transcripts — synthesis only
## Notes Distribution
**Subject Line Format**: "[Meeting Type] Notes - [Date] - [Key Topic]"
plugins/pm-essentials/skills/prd-template/SKILL.md
+20 -1
View File
@@ -1,12 +1,22 @@
---
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.
description: "Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics."
---
# PRD Template Skill
This skill helps create professional Product Requirements Documents following industry best practices.
## Required Inputs
Ask the user for these if not provided:
- **Feature or product name**
- **Problem being solved** (from the user's perspective)
- **Target user** (role, context, what they're trying to accomplish)
- **Success metrics** (how will you know it worked?)
- **Scope** (MVP vs full vision — what's in and out of scope)
- **Key stakeholders** (who needs to review and approve)
## Template Structure
Every PRD should include these sections in order:
@@ -91,6 +101,15 @@ Format: "As a [user type], I want to [action] so that [benefit]"
- Skip the "why"
- Forget about accessibility
## Quality Checks
- [ ] Problem statement is written from the user's perspective (not the company's)
- [ ] Success metrics are specific and measurable
- [ ] User stories include acceptance criteria
- [ ] Requirements are testable (not vague)
- [ ] Open questions are listed explicitly
- [ ] Implementation plan distinguishes MVP from future phases
## Example PRD Opening
```
plugins/pm-essentials/skills/stakeholder-update/SKILL.md
+18 -1
View File
@@ -1,12 +1,21 @@
---
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.
description: "Create concise executive stakeholder updates using the BLUF (Bottom Line Up Front) framework. Use when asked to write a status update, progress report, project communication, or executive briefing for leadership or stakeholders. Produces a BLUF-led update with status, key metrics, risks, upcoming milestones, and decisions needed — readable in under 2 minutes."
---
# Stakeholder Update Skill
This skill creates effective status updates for executives and stakeholders following the BLUF (Bottom Line Up Front) principle.
## Required Inputs
Ask the user for these if not provided:
- **Project or product being reported on**
- **Audience** (CEO, board, cross-functional leads, investors — changes depth and format)
- **Period** (this week / this sprint / this month)
- **Current status** (on track / at risk / blocked)
- **Key metrics** and their current values vs. targets
## Update Structure
### 1. BLUF (Bottom Line Up Front)
@@ -217,3 +226,11 @@ Only include issues that matter at executive level.
- Competitive positioning
- Market opportunities
- Financial implications
## Quality Checks
- [ ] Update leads with BLUF — status, key takeaway, and action needed before any detail
- [ ] Every metric has a target comparison (not just a raw number)
- [ ] Every risk has a mitigation and a "help needed" flag if stakeholder action is required
- [ ] Decisions needed have specific options and a clear recommendation
- [ ] Total length is under 1 page / 2 minutes reading time
plugins/pm-essentials/skills/user-research-synthesis/SKILL.md
+9 -1
View File
@@ -1,12 +1,20 @@
---
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.
description: "Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps."
---
# User Research Synthesis Skill
This skill helps analyze user research data and transform it into actionable insights following a structured methodology.
## Required Inputs
Ask the user for these if not provided:
- **Research data** (transcripts, notes, survey results, or summary bullets)
- **Research method** (interviews, surveys, usability tests, etc.)
- **Number of participants** and their profiles (role, context)
- **Research questions** the study aimed to answer
## Synthesis Framework
### 1. Data Collection Overview