fix: update marketplace.json to v4.0.0 with 14 plugins

feat: add 6 new plugin bundles (pm-gtm, pm-engineering, pm-data, pm-people, pm-design, pm-business)
add folders in plugins
2026-04-02 09:54:42 +01:00 · 2026-04-02 09:35:59 +01:00 · 2026-04-02 09:19:07 +01:00 · 2026-04-02 09:04:17 +01:00 · 2026-04-02 09:01:04 +01:00 · 2026-04-02 13:24:30 +05:30
140 changed files with 11867 additions and 406 deletions
@@ -0,0 +1,124 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "pm-claude-skills",
+  "version": "4.0.0",
+  "description": "53 Claude Skills across 6 professions — product management, marketing, engineering, data, design, and leadership. Save 10-15 hours per week.",
+  "owner": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "plugins": [
+    {
+      "name": "pm-essentials",
+      "description": "Core PM skills: PRD Template, Meeting Notes, Stakeholder Update, User Research Synthesis, Competitive Analysis. The 5 skills every PM needs first.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-essentials",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-discovery",
+      "description": "Discovery & research skills: Discovery Interview Guide, Job Story Mapper, User Interview Synthesis, Assumption Mapper. Structure user research from screener to synthesis.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-discovery",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-planning",
+      "description": "Planning & strategy skills: OKR Builder, Feature Prioritisation (RICE/MoSCoW/Kano/ICE), Roadmap Presentation, Pricing Strategy, RICE + Impact Matrix, Roadmap Narrative.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-planning",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-delivery",
+      "description": "Sprint & delivery skills: Sprint Planning, Technical Spec Template, A/B Test Planner, Go-to-Market Planner, Product Launch Checklist, Sprint Brief, Retro Analysis.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-delivery",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-analytics",
+      "description": "Data & metrics skills: Data Analysis Standard, Retention Analysis, Product Health Analysis. Structure metric deep-dives, funnel analysis, cohort studies and churn investigations.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-analytics",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-strategy",
+      "description": "Strategy & stakeholder skills: Competitor Signal Tracker, Competitive Intelligence Monitor, Stakeholder Influence Mapper, Strategic Narrative Generator, Executive Update, Ambiguity Resolver.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-strategy",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-advanced",
+      "description": "Advanced PM skills: AI Product Canvas, Multi-Source Signal Synthesiser, Experiment Designer, Design Handoff Brief, Stakeholder Update. For senior PMs working on complex products.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-advanced",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-rituals",
+      "description": "Weekly PM ritual skill: PM Weekly Review. A 20-minute structured ritual covering metrics, shipping progress, insights, and next week's top 3 priorities.",
+      "version": "3.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-rituals",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-gtm",
+      "description": "Marketing & GTM skills: Go-To-Market Planner, Content Calendar, Competitor Teardown, Email Campaign. Build positioning statements, messaging pillars, feature lists, use cases, and launch campaigns.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-gtm",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-engineering",
+      "description": "Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record. Structured outputs for engineering teams and technical PMs.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-engineering",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-data",
+      "description": "Data & analytics skills: Metrics Framework, SQL Query Explainer, Dashboard Brief. Build North Star metric trees, explain and optimise SQL, and spec dashboards from business questions.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-data",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-people",
+      "description": "Leadership & people skills: Performance Review, Hiring Rubric, Team Offsite Planner. Write structured reviews, build interview scorecards, and plan offsites from goals to minute-by-minute agenda.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-people",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-design",
+      "description": "Design & UX skills: UX Research Plan, Design Critique, Accessibility Audit. Create research plans with discussion guides, critique designs using JTBD and Gestalt principles, audit for WCAG 2.2 compliance.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-design",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-business",
+      "description": "Business & strategy skills: Investor Update, Board Deck Narrative, Job Application. Write investor updates investors actually read, structure board presentations, and tailor CVs with ATS optimisation.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-business",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    }
+  ]
+}
@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: mohit15856
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
@@ -1,197 +1,164 @@
-# Contributing to PM Claude Skills
+# Contributing to pm-claude-skills

-Thank you for considering contributing to PM Claude Skills! This document provides guidelines for contributing.
+Thank you for wanting to contribute. This repo grows through community submissions — every profession added makes it more useful for everyone.

-## Ways to Contribute
-
-### 1. Report Bugs 🐛
-
-If you find a bug in a Skill:
-
-1. Check if the issue already exists in [Issues](https://github.com/mohitagw15856/pm-claude-skills/issues)
-2. If not, create a new issue using the Bug Report template
-3. Include:
-   - Which Skill has the issue
-   - What you expected to happen
-   - What actually happened
-   - Steps to reproduce
-   - Your Claude version (Pro/Team/Enterprise)
-
-### 2. Request Skills 💡
-
-Have an idea for a new Skill?
-
-1. Check [existing issues](https://github.com/mohitagw15856/pm-claude-skills/issues?q=is%3Aissue+label%3Aenhancement) to avoid duplicates
-2. Create a new issue using the Skill Request template
-3. Describe:
-   - What PM task the Skill would help with
-   - How you currently do this task
-   - Time you spend on it
-   - Example outputs
-
-### 3. Improve Documentation 📚
-
-Documentation improvements are always welcome:
-
- Fix typos or unclear instructions
- Add examples
- Improve installation guides
- Share your use cases
-
-### 4. Submit Skills 🎁
-
-Want to contribute a Skill you've created?
-
-**Requirements:**
- Skill must be PM-related
- Include complete SKILL.md with proper frontmatter
- Provide examples of outputs
- Must be tested and working
- Include documentation
-
-**Process:**
-1. Fork the repository
-2. Create a new branch: `git checkout -b skill/your-skill-name`
-3. Add your Skill to `skills/your-skill-name/`
-4. Update main README.md to list your Skill
-5. Submit a Pull Request
-
-### 5. Improve Existing Skills 🔧
-
-Found a way to make a Skill better?
-
-1. Fork the repository
-2. Make your improvements
-3. Test thoroughly
-4. Submit a Pull Request with:
-   - Clear description of changes
-   - Why the change improves the Skill
-   - Before/after examples if applicable
-
-## Skill Contribution Guidelines
-
-### Structure
-
-Every Skill must follow this structure:
-
-```
-skill-name/
-├── SKILL.md (required)
-└── [other resources as needed]
-```
-
-### SKILL.md Format
-
-```markdown
---
-name: skill-name
-description: Clear description of what the skill does and when to use it. This is critical - Claude uses this to decide when to trigger the skill.
 ---

-# Skill Name
+## What We're Looking For

-[Detailed instructions for using the skill]
+Good skills have three things in common:

-## Structure/Template
+1. **They solve a recurring workflow** — not a one-off task. If you do this thing more than once a week and it follows a consistent structure, it's probably a good skill candidate.
+2. **They have a clear trigger** — Claude needs to know when to activate the skill. The `description` in your frontmatter is what Claude reads to decide if your skill is relevant. Make it specific.
+3. **They produce structured, useful output** — the output should be something you'd actually use at work, not a generic response.

-[The format/structure the skill should follow]
+---

-## Guidelines
+## How to Submit a Skill

-[Best practices and tips]
+### Step 1: Fork the repo

-## Examples
+Click **Fork** in the top right of the GitHub repo. This creates your own copy.

-[Example outputs]
-```
+### Step 2: Clone your fork

-### Quality Standards
+git clone https://github.com/YOUR_USERNAME/pm-claude-skills.git
+cd pm-claude-skills

-Skills should:
- ✅ Be well-documented and clear
- ✅ Include concrete examples
- ✅ Follow PM best practices
- ✅ Save meaningful time (not trivial tasks)
- ✅ Be tested and working
- ✅ Be general enough for others to use
- ❌ Not include proprietary company information
- ❌ Not require external tools (unless clearly documented)

-## Pull Request Process
+### Step 3: Create your skill folder

-1. **Fork & Branch**
-   ```bash
-   git clone https://github.com/mohitagw15856/pm-claude-skills.git
-   cd pm-claude-skills
-   git checkout -b feature/your-feature-name
-   ```
+Skills live in the `skills/` directory. Create a folder named after your skill using lowercase and hyphens:

-2. **Make Changes**
-   - Follow existing code style
-   - Update documentation
-   - Add examples
+mkdir skills/your-skill-name

-3. **Test**
-   - Test the Skill in Claude
-   - Verify it works as expected
-   - Check for edge cases

-4. **Commit**
-   ```bash
-   git add .
-   git commit -m "Add: Brief description of changes"
-   ```
+**Naming rules:**
+- Lowercase only
+- Hyphens between words (no underscores, no spaces)
+- Descriptive but concise: `legal-contract-review` not `skill-for-reviewing-legal-contracts`

-5. **Push & Create PR**
-   ```bash
-   git push origin feature/your-feature-name
-   ```
-   Then create a Pull Request on GitHub
+### Step 4: Create your SKILL.md

-6. **PR Description Should Include:**
-   - What changes you made
-   - Why you made them
-   - How to test them
-   - Screenshots/examples (if applicable)
+Every skill needs exactly one file: `SKILL.md` (uppercase, `.md` extension).

-## Code of Conduct
+**Minimum required structure:**

-### Our Standards
+---
+name: your-skill-name
+description: "One sentence. Use when [trigger condition]. Produces [output description]."
+---

- Be respectful and inclusive
- Welcome newcomers
- Accept constructive criticism
- Focus on what's best for the community
- Show empathy towards others
+# Skill Title

-### Unacceptable Behavior
+[Your skill instructions here]

- Harassment or discriminatory language
- Trolling or insulting comments
- Personal or political attacks
- Publishing private information
- Unprofessional conduct

-### Enforcement
+**The description field is the most important part.** It's what Claude reads (~100 tokens) to decide if your skill is relevant. Write it like this:

-Violations may result in:
-1. Warning
-2. Temporary ban
-3. Permanent ban
+✅ Good: `"Write structured incident postmortems. Use when asked for a postmortem, RCA, incident report, or P1/P2 review. Produces a blameless postmortem with timeline, root cause, impact, and action items."`

-Report violations to: [mohit15856@gmail.com]
+❌ Too vague: `"Helps with incident reports."`
+
+**Full recommended structure for a quality skill:**
+
+---
+name: your-skill-name
+description: "..."
+---
+
+# Skill Title
+
+Brief description of what this skill does.
+
+## Required Inputs
+
+What Claude should ask for if the user doesn't provide it.
+
+## Output Structure
+
+The exact format and sections Claude should produce.
+
+## Quality Checks
+
+A checklist Claude runs before delivering output.
+
+## Example Trigger Phrases
+
+- "Example phrase that would activate this skill"
+- "Another example"
+
+
+### Step 5: Test your skill locally
+
+Before submitting:
+
+1. Copy your skill folder to `~/.claude/skills/`
+2. Open Claude Code
+3. Try your example trigger phrases
+4. Verify the output matches what your SKILL.md describes
+5. Adjust and refine until it's working well
+
+### Step 6: Commit and push
+
+git add skills/your-skill-name/SKILL.md
+git commit -m "feat: add [skill-name] skill for [profession/use case]"
+git push origin main
+
+
+### Step 7: Open a Pull Request
+
+Go to your fork on GitHub and click **"Compare & pull request"**.
+
+In your PR description, include:
+- **What the skill does** (1–2 sentences)
+- **Who it's for** (profession or role)
+- **Why you built it** (what workflow pain does it solve?)
+- **Example output** (paste a sample or screenshot — helps with review)
+
+---
+
+## Review Process
+
+- PRs are reviewed weekly (usually Fridays)
+- Feedback will be left as PR comments — usually requesting a description improvement or output structure refinement
+- Once approved, your skill is merged and added to the README
+- Your GitHub handle is added to the Contributors section
+
+---
+
+## What Gets Rejected
+
+- Skills with vague descriptions that would trigger on too many unrelated tasks
+- Skills that just wrap a single simple prompt (a skill should have structure and logic)
+- Duplicate skills — check the existing skills list before submitting
+- Skills that require external API keys or services not everyone has access to (unless clearly documented)
+
+---
+
+## Skills Wishlist
+
+These have been requested but not yet built. Pick one up if you have the expertise:
+
+| Skill | Use case |
+|---|---|
+| `legal-contract-review` | Flag key clauses and risks in contracts |
+| `financial-model-narrative` | Turn spreadsheet outputs into board-ready narrative |
+| `hr-job-description` | Write inclusive, structured JDs from a role brief |
+| `onboarding-plan` | 30/60/90-day plan for new hires |
+| `press-release` | Structured press releases from product announcements |
+| `seo-content-brief` | Content briefs with keyword strategy and outline |
+| `grant-proposal` | Structure grant applications for nonprofits and researchers |
+| `sales-battlecard` | Competitive battlecards for sales teams |
+
+Suggest a new skill: [Open an issue](../../issues/new) with the label `skill-request`.
+
+---

 ## Questions?

- 💬 Start a [Discussion](https://github.com/mohitagw15856/pm-claude-skills/discussions)
- ✉️ Email: [mohit15856@gmail.com]
- 🐦 Twitter: [@yourhandle]
+Open a [Discussion](../../discussions) or raise an [Issue](../../issues). Happy to help you get a skill PR-ready.

-## Recognition
+---

-Contributors will be:
- Listed in the project README
- Credited in the Skill they contributed
- Mentioned in release notes
-
-Thank you for contributing! 🙏
+*Thank you for contributing. Every skill added here saves someone an hour they'd rather spend on something else.*
@@ -40,10 +40,9 @@ Get your first PM Skill working in 5 minutes.

 Start a new conversation and try:

-```
 Help me write a PRD for a mobile app feature 
 that lets users save articles for later reading
-```
+

 Claude should automatically use the PRD Template Skill and create a structured PRD.

@@ -1,247 +1,178 @@
-# Product Management Claude Skills
+# 🧠 Claude Skills Library — 53 Skills for Every Professional

-**Transform your PM workflow with specialized Claude Skills for common product management tasks.**
+> **Save 8–10 hours per week across any profession. Install in 2 minutes.**

-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![GitHub stars](https://img.shields.io/github/stars/mohitagw15856/pm-claude-skills.svg)](https://github.com/mohitagw15856/pm-claude-skills/stargazers)
-
-> 📖 **Background**: These Skills emerged from two Medium articles: [Part 1 — How Skills changed my workflow](https://medium.com/product-powerhouse/claude-skills-the-ai-feature-thats-quietly-changing-how-product-managers-work-aad5d8d0640a) and [Part 2 — The complete 12-skill toolkit](https://medium.com/@mohit15856/12-claude-skills-for-product-managers-the-complete-toolkit-with-skill-files-for-jira-figma-fcc73a4c1e58).
-
-## 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, Team, or Enterprise account
-2. **Enable Code Execution**: Settings → Features → Enable "Code Execution and File Creation"
-3. **Install Your First Skill**:
-   - Download the [`prd-template`](skills/prd-template) folder
-   - Zip the folder (it should contain SKILL.md and any other files)
-   - Rename the .zip to .skill (e.g., `prd-template.skill`)
-   - Go to claude.ai → Settings → Skills → Upload Skill
-   - 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 | Folder |
-|-------|---------|------------|--------|
-| **PRD Template** | Standardized product requirements | 2-3 hrs/PRD | [View](skills/prd-template) |
-| **Meeting Notes** | Structured meeting documentation | 15-30 min/meeting | [View](skills/meeting-notes) |
-| **Stakeholder Update** | Executive status updates | 30-45 min/update | [View](skills/stakeholder-update) |
-| **User Research Synthesis** | Analyze and synthesize research findings | 2-3 hrs/study | [View](skills/user-research-synthesis) |
-| **Competitive Analysis** | Structured competitive assessments | 1-2 hrs/analysis | [View](skills/competitive-analysis) |
-
-### Discovery & User Research
-| **User Interview Synthesis** | Synthesise transcripts into structured findings | Notion | [View](skills/user-interview-synthesis) |
-| **Assumption Mapper** | Risk-rate hidden assumptions in any PRD | Miro | [View](skills/assumption-mapper) |
-
-### Roadmapping & Prioritisation
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **RICE Prioritisation** | Score and rank initiatives objectively | Jira | [View](skills/rice-prioritisation) |
-| **Roadmap Narrative** | Turn ranked lists into strategic narratives | Notion, Miro | [View](skills/roadmap-narrative) |
-| **RICE + Impact Matrix** | RICE scoring + strategic alignment combined | Miro, Jira | [View](skills/rice-impact-matrix) |
-
-### Sprint & Delivery
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **Sprint Brief** | Generate sprint briefs from Jira data | Jira, Slack | [View](skills/sprint-brief) |
-| **Retro Analysis** | Data-grounded retrospective briefs | Jira, Miro | [View](skills/retro-analysis) |
-
-### Data & Metrics
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **Product Health Analysis** | Interpret metrics and surface signals | Analytics | [View](skills/product-health-analysis) |
-
-### Strategy & Competitive Intel
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **Competitor Signal Tracker** | Analyse competitor moves strategically | Notion | [View](skills/competitor-signal-tracker) |
-
-### Stakeholder Communication
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **PRD Template** | Standardized product requirements | — | [View](skills/prd-template) |
-| **Meeting Notes** | Structured meeting documentation | — | [View](skills/meeting-notes) |
-| **Stakeholder Update** | Executive status updates | — | [View](skills/stakeholder-update) |
-| **Executive Update** | Sharp executive briefings | Slack, Teams | [View](skills/executive-update) |
-
-### Go-to-Market & Launch
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **Launch Readiness** | Pre-launch go/no-go assessment | Notion, Jira, Slack | [View](skills/launch-readiness) |
-
-### Cross-functional Collaboration
-| Skill | Purpose | Tool | Folder |
-|-------|---------|------|--------|
-| **User Research Synthesis** | Analyze and synthesize research findings | Notion | [View](skills/user-research-synthesis) |
-| **Competitive Analysis** | Structured competitive assessments | — | [View](skills/competitive-analysis) |
-| **Design Handoff Brief** | PM-to-designer structured briefs | Figma, Notion | [View](skills/design-handoff-brief) |
-
-
-Want a specific Skill? [Request it here](https://github.com/mohitagw15856/pm-claude-skills/issues/new?template=skill-request.md)
-
-## 💡 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
- [Troubleshooting](docs/troubleshooting.md) - Common issues and fixes
- [Creating Your Own Skills](docs/creating-skills.md) - Build custom Skills
-
-## 🛠️ Installation
-
-### Method 1: Download Individual Skills (Easiest)
-
-1. Navigate to the skill folder (e.g., `skills/prd-template`)
-2. Download all files in that folder
-3. Create a zip file containing those files
-4. Rename from `.zip` to `.skill`
-5. Upload to Claude via Settings → Skills
-
-### Method 2: Clone the Repo
-
-bash
-# Clone the repository
-git clone https://github.com/mohitagw15856/pm-claude-skills.git
-cd pm-claude-skills
-
-# Package a skill (creates .skill file)
-cd skills/prd-template
-zip -r ../../prd-template.skill .
-cd ../..
-
-# Now upload prd-template.skill to Claude
-
-
-### Method 3: Direct Download (When Available)
-
-Check the [Releases](https://github.com/mohitagw15856/pm-claude-skills/releases) page for pre-packaged `.skill` files.
-
-## 🎓 How to Use
-
-1. **Upload a Skill**: Follow installation instructions above
-2. **Just ask Claude**: Claude will automatically recognize when to use the Skill
-   - "Help me write a PRD for X"
-   - "Take notes from this meeting transcript"
-   - "Create a competitive analysis of X, Y, Z"
-3. **No special commands needed**: Skills activate automatically based on context
-
-## 🔧 Customization
-
-Every company has different formats and processes. These Skills are designed to be customized:
-
-1. Download the Skill folder
-2. Edit the `SKILL.md` file to match your standards
-3. Add your company's examples to the instructions
-4. Re-package and upload
-
-See the [Customization Guide](docs/customization.md) for detailed instructions.
-
-## 🤝 Contributing
-
-Found a bug? Want to suggest an improvement? Contributions are welcome!
-
- 🐛 [Report an Issue](https://github.com/mohitagw15856/pm-claude-skills/issues/new?template=bug-report.md)
- 💡 [Request a Skill](https://github.com/mohitagw15856/pm-claude-skills/issues/new?template=skill-request.md)
- 🔀 [Submit a Pull Request](https://github.com/mohitagw15856/pm-claude-skills/pulls)
- 💬 [Join Discussions](https://github.com/mohitagw15856/pm-claude-skills/discussions)
-
-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
-
-**Q1 2026:**
- [ ] Add Data Analysis Standard Skill
- [ ] Add Roadmap Presentation Skill
- [ ] Create video tutorials
- [ ] Pre-packaged .skill files in Releases
-
-**Q2 2026:**
- [ ] Domain-specific Skills (SaaS PM, B2B PM, Growth PM)
- [ ] Team collaboration Skills
- [ ] Notion/Confluence template packs
-
-**Long-term:**
- [ ] Interactive Skill builder tool
- [ ] Integration examples with PM tools
- [ ] 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, 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 a Skill doesn't work?**  
-A: Check [Troubleshooting](docs/troubleshooting.md) or [open an issue](https://github.com/mohitagw15856/pm-claude-skills/issues).
-
-**Q: How do I create my own Skills?**  
-A: See [Creating Your Own Skills](docs/creating-skills.md) for a complete guide.
-
-**Q: Can I use these commercially?**  
-A: Yes! MIT license allows commercial use.
-
-## 🔗 Links
-
- 📝 [Original Medium Article](https://medium.com/product-powerhouse/claude-skills-the-ai-feature-thats-quietly-changing-how-product-managers-work-aad5d8d0640a)
- 💼 [Connect on LinkedIn](www.linkedin.com/in/mohitaggarwal4)
- ✉️ [Email me](mailto:mohit15856@gmail.com)
- Writing these up and refining them took a fair few evenings. If they saved you some time, a [coffee](https://buymeacoffee.com/mohit15856) is always appreciated 
-
-## 🙏 Acknowledgments
-
-Thank you to everyone who read and shared my Medium article, and to the Anthropic team for building such a powerful feature.
-
-Special thanks to the early testers who provided feedback on these Skills.
+A community-built library of Claude Skills covering product management, marketing, engineering, data, design, leadership, and business strategy. Each skill is a structured SKILL.md file that teaches Claude how to produce professional-grade outputs for your specific workflows.

 ---

-**Made with ☕ by [Mohit Aggarwal](https://mohit-pm.netlify.app/)**
+## 🚀 Quick Install (2 minutes)

-*Helping product managers work smarter with AI*
+In Claude Code, run:

-⭐ **Star this repo to get updates as new Skills are added!**
+/plugin marketplace add mohitagw15856/pm-claude-skills
+
+
+Or clone and symlink for auto-updates:
+
+git clone https://github.com/mohitagw15856/pm-claude-skills.git ~/pm-claude-skills
+mkdir -p ~/.claude/skills
+ln -s ~/pm-claude-skills/skills/* ~/.claude/skills/
+
+
+That's it. All 53 skills are now available in every Claude Code session.
+
+---
+
+## 📚 The Article Series
+
+This repo was built alongside a published article series. Read the full story:
+
+| Part | Title | Link |
+|---|---|---|
+| Part 1 | Claude Skills: The AI Feature That's Quietly Changing How PMs Work | [Read →](https://medium.com/product-powerhouse/claude-skills-the-ai-feature-thats-quietly-changing-how-product-managers-work-aad5d8d0640a) |
+| Part 2 | Claude Skills vs Prompts: How PMs and Developers Can 10x Their AI Productivity | [Read →](https://medium.com/@mohit15856/claude-skills-vs-prompts-how-pms-and-developers-can-10x-their-ai-productivity-facb5eed5b12) |
+| Part 3 | 12 Claude Skills for Product Managers: The Complete Toolkit | [Read →](https://medium.com/@mohit15856/12-claude-skills-for-product-managers-the-complete-toolkit-with-skill-files-for-jira-figma-fcc73a4c1e58) |
+| Part 4 | Claude Skills: Advanced Guide — What 3 Months of Daily PM Use Actually Taught Me | [Read →](https://medium.com/@mohit15856/claude-skills-advanced-guide-what-3-months-of-daily-pm-use-actually-taught-me-18324d6ef7bc) |
+| Part 5 | What Google, Meta and Anthropic Want From PMs — And the Claude Skills That Deliver It | [Read →](https://medium.com/@mohit15856/what-google-meta-and-anthropic-want-from-pms-and-the-claude-skills-that-deliver-it-b0f2b6cd9340) |
+| Part 6 | I Tested Anthropic's Skill Creator Plugin on My Own Skills | [Read →](https://medium.com/all-about-claude/i-tested-anthropics-skill-creator-plugin-on-my-own-skills-here-s-what-i-found-23ad406b0825) |
+| Part 7 | 33 Claude Skills for PMs Are Now in the Claude Code Marketplace | [Read →](https://medium.com/product-powerhouse/33-claude-skills-for-pms-are-now-in-the-claude-code-marketplace-heres-how-to-install-them-7968ab6bb1e1) |
+| Part 8 | I Added 20 New Claude Skills Beyond Product Management | *Latest — link TBC* |
+
+---
+
+## 🗂️ All 53 Skills
+
+### 🛠️ Product Management (Skills 1–33)
+
+> The original toolkit. Discovery, prioritisation, delivery, strategy, stakeholder comms, and more.
+
+| # | Skill | What It Does |
+|---|---|---|
+| 1–33 | *[Original 33 PM skills]* | See [Part 7 article](https://medium.com/product-powerhouse/33-claude-skills-for-pms-are-now-in-the-claude-code-marketplace-heres-how-to-install-them-7968ab6bb1e1) for full list |
+
+---
+
+### 📣 Marketing & Growth (Skills 34–37)
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 34 | **Go-To-Market** | `skills/go-to-market/` | Positioning statements, messaging pillars, feature/benefit mapping, and role-specific use cases |
+| 35 | **Content Calendar** | `skills/content-calendar/` | Multi-channel content calendars with hooks, formats, and repurposing map |
+| 36 | **Competitor Teardown** | `skills/competitor-teardown/` | Full competitive analysis: positioning map, feature comparison, messaging gaps, SWOT, recommendations |
+| 37 | **Email Campaign** | `skills/email-campaign/` | Sequenced email campaigns with subject lines, preview text, body copy, and CTAs |
+
+---
+
+### 👩‍💻 Engineering & Tech (Skills 38–41)
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 38 | **Code Review Checklist** | `skills/code-review-checklist/` | Tailored PR review checklists by language, type, and risk level |
+| 39 | **Incident Postmortem** | `skills/incident-postmortem/` | Blameless postmortems with timeline, RCA, impact, and action items |
+| 40 | **API Docs Writer** | `skills/api-docs-writer/` | Developer-facing API docs from raw specs: endpoints, parameters, response schemas, code examples |
+| 41 | **Architecture Decision Record** | `skills/architecture-decision-record/` | ADRs with context, options, decision, consequences, and risks |
+
+---
+
+### 📊 Data & Analytics (Skills 42–44)
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 42 | **Metrics Framework** | `skills/metrics-framework/` | North Star + metric tree, dashboard tiers, counter-metrics |
+| 43 | **SQL Query Explainer** | `skills/sql-query-explainer/` | Explain, optimise, write, and document SQL — in plain English |
+| 44 | **Dashboard Brief** | `skills/dashboard-brief/` | Complete dashboard spec: KPIs, charts, filters, layout, data requirements |
+
+---
+
+### 🧑‍💼 Leadership & Management (Skills 45–47)
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 45 | **Performance Review** | `skills/performance-review/` | Structured reviews from bullet-point notes — self, manager, peer, and upward |
+| 46 | **Hiring Rubric** | `skills/hiring-rubric/` | Interview scorecards with competencies, behavioural questions, and panel guide |
+| 47 | **Team Offsite Planner** | `skills/team-offsite-planner/` | Full offsite agenda, session facilitation notes, and logistics checklist |
+
+---
+
+### 🎨 Design & UX (Skills 48–50)
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 48 | **UX Research Plan** | `skills/ux-research-plan/` | Research plans with screener, discussion guide, and synthesis framework |
+| 49 | **Design Critique** | `skills/design-critique/` | Structured feedback using JTBD, Gestalt principles, and Nielsen's heuristics |
+| 50 | **Accessibility Audit** | `skills/accessibility-audit/` | WCAG 2.2 audit with prioritised remediation and quick wins |
+
+---
+
+### 🏢 Business & Strategy (Skills 51–53)
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 51 | **Investor Update** | `skills/investor-update/` | Monthly/quarterly investor updates: metrics, highlights, challenges, and asks |
+| 52 | **Board Deck Narrative** | `skills/board-deck-narrative/` | Slide-by-slide board presentation structure with narrative beats and talking points |
+| 53 | **Job Application** | `skills/job-application/` | Tailored CV summary, ATS keyword optimisation, and cover letter for any JD |
+
+---
+
+## 🤝 Contributing — Add Your Skill
+
+This is an open-source community library. If you've built a skill that saves you time, share it here.
+
+**How to contribute:**
+
+1. Fork this repo
+2. Create a new folder: `skills/your-skill-name/`
+3. Add a `SKILL.md` file following the template below
+4. Raise a pull request with a short description of what the skill does and why you built it
+
+**SKILL.md template:**
+---
+name: your-skill-name
+description: "One sentence description. Use when [trigger condition]. Does [output description]."
+---
+
+# Skill Title
+
+[Instructions for Claude to follow when this skill is invoked]
+
+
+**What makes a good skill:**
+- Solves a recurring professional workflow (not a one-off task)
+- Has a clear trigger description so Claude knows when to activate it
+- Produces consistent, structured output
+- Works without needing extensive setup or context
+
+**Skills wishlist** (most requested — up for grabs):
+- `legal-contract-review` — Flag key clauses and risks in contracts
+- `financial-model-narrative` — Turn a spreadsheet into a board-ready narrative
+- `hr-job-description` — Write inclusive, structured JDs from a role brief
+- `onboarding-plan` — 30/60/90-day plan for new hires
+- `press-release` — Structured press releases from product announcements
+- `seo-content-brief` — Content briefs with keyword strategy and outline
+
+Have a skill idea? [Open an issue](../../issues) or raise it in [Discussions](../../discussions).
+
+**Contributors** get credited in this README and in the article series. 🙌
+
+---
+
+## 📖 How Skills Work
+
+Skills are markdown files in `~/.claude/skills/` that Claude reads dynamically. When you describe a task, Claude scans available skill descriptions (~100 tokens) and loads the full skill only when it's relevant. This means:
+
+- Skills are efficient — they only use tokens when triggered
+- Multiple skills can coexist without slowing Claude down
+- Personal skills (`~/.claude/skills/`) work across all your projects
+
+Learn more: [Anthropic's Skills documentation](https://code.claude.com/docs/en/skills)
+
+---
+
+## ⭐ If this is useful
+
+Star the repo so others can find it. And if you build something with these skills, share it — raise a PR, open a discussion, or tag me in your article.
+
+---
+
+*Built and maintained by [Mohit Aggarwal](https://medium.com/@mohit15856) | [Product Powerhouse publication](https://medium.com/product-powerhouse)*
@@ -0,0 +1,205 @@
+#!/bin/bash
+# Run from your repo root: cd pm-claude-skills && bash add-plugin-json.sh
+# Writes plugin.json into every bundle's .claude-plugin/ folder, commits, and pushes.
+
+echo "=== Writing plugin.json for all 8 bundles ==="
+
+# ─────────────────────────────────────────
+# BUNDLE 1: pm-essentials
+# ─────────────────────────────────────────
+cat > plugins/pm-essentials/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-essentials",
+  "version": "3.0.0",
+  "description": "Core PM skills: PRD Template, Meeting Notes, Stakeholder Update, User Research Synthesis, and Competitive Analysis. The 5 skills every PM needs first.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "prd", "meeting-notes", "stakeholder", "user-research", "competitive-analysis"]
+}
+EOF
+echo "✓ pm-essentials/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 2: pm-discovery
+# ─────────────────────────────────────────
+cat > plugins/pm-discovery/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-discovery",
+  "version": "3.0.0",
+  "description": "Discovery & research skills: Discovery Interview Guide, Job Story Mapper, User Interview Synthesis, Assumption Mapper. Structure user research from screener to synthesis.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "user-research", "discovery", "jtbd", "interviews", "assumption-mapping"]
+}
+EOF
+echo "✓ pm-discovery/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 3: pm-planning
+# ─────────────────────────────────────────
+cat > plugins/pm-planning/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-planning",
+  "version": "3.0.0",
+  "description": "Planning & strategy skills: OKR Builder, Feature Prioritisation (RICE/MoSCoW/Kano/ICE), Roadmap Presentation, Pricing Strategy, RICE + Impact Matrix, Roadmap Narrative.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "okr", "prioritisation", "roadmap", "pricing", "rice", "moscow", "kano"]
+}
+EOF
+echo "✓ pm-planning/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 4: pm-delivery
+# ─────────────────────────────────────────
+cat > plugins/pm-delivery/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-delivery",
+  "version": "3.0.0",
+  "description": "Sprint & delivery skills: Sprint Planning, Technical Spec Template, A/B Test Planner, Go-to-Market Planner, Product Launch Checklist, Sprint Brief, Retro Analysis.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "sprint", "agile", "ab-testing", "go-to-market", "launch", "technical-spec"]
+}
+EOF
+echo "✓ pm-delivery/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 5: pm-analytics
+# ─────────────────────────────────────────
+cat > plugins/pm-analytics/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-analytics",
+  "version": "3.0.0",
+  "description": "Data & metrics skills: Data Analysis Standard, Retention Analysis, Product Health Analysis. Structure metric deep-dives, funnel analysis, cohort studies and churn investigations.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "analytics", "retention", "metrics", "funnel", "cohort", "churn"]
+}
+EOF
+echo "✓ pm-analytics/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 6: pm-strategy
+# ─────────────────────────────────────────
+cat > plugins/pm-strategy/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-strategy",
+  "version": "3.0.0",
+  "description": "Strategy & stakeholder skills: Competitor Signal Tracker, Competitive Intelligence Monitor, Stakeholder Influence Mapper, Strategic Narrative Generator, Executive Update, Ambiguity Resolver.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "strategy", "competitive-intelligence", "stakeholder", "executive", "narrative"]
+}
+EOF
+echo "✓ pm-strategy/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 7: pm-advanced
+# ─────────────────────────────────────────
+cat > plugins/pm-advanced/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-advanced",
+  "version": "3.0.0",
+  "description": "Advanced PM skills: AI Product Canvas, Multi-Source Signal Synthesiser, Experiment Designer, Design Handoff Brief. For senior PMs working on complex or AI-powered products.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "ai-product", "experiment-design", "design-handoff", "signal-synthesis"]
+}
+EOF
+echo "✓ pm-advanced/plugin.json written"
+
+# ─────────────────────────────────────────
+# BUNDLE 8: pm-rituals
+# ─────────────────────────────────────────
+cat > plugins/pm-rituals/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-rituals",
+  "version": "3.0.0",
+  "description": "PM Weekly Review: a 20-minute structured ritual covering metrics movement, shipping progress, customer insights, and next week's top 3 priorities in a shareable update.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "weekly-review", "productivity", "rituals", "planning"]
+}
+EOF
+echo "✓ pm-rituals/plugin.json written"
+
+# ─────────────────────────────────────────
+# COMMIT AND PUSH
+# ─────────────────────────────────────────
+echo ""
+echo "=== All 8 plugin.json files written ==="
+echo ""
+echo "=== Committing and pushing ==="
+
+git add plugins/pm-essentials/.claude-plugin/plugin.json
+git add plugins/pm-discovery/.claude-plugin/plugin.json
+git add plugins/pm-planning/.claude-plugin/plugin.json
+git add plugins/pm-delivery/.claude-plugin/plugin.json
+git add plugins/pm-analytics/.claude-plugin/plugin.json
+git add plugins/pm-strategy/.claude-plugin/plugin.json
+git add plugins/pm-advanced/.claude-plugin/plugin.json
+git add plugins/pm-rituals/.claude-plugin/plugin.json
+
+git commit -m "add plugin.json manifests for all 8 PM skill bundles"
+git push
+
+echo ""
+echo "=== Pushed! Now re-adding the marketplace in Claude Code ==="
+echo ""
+echo "Run these commands inside Claude Code:"
+echo ""
+echo "  /plugin marketplace remove mohitagw15856/pm-claude-skills"
+echo "  /plugin marketplace add mohitagw15856/pm-claude-skills"
+echo ""
+echo "Then install any bundle you want:"
+echo "  /plugin install pm-essentials@pm-claude-skills"
+echo "  /plugin install pm-discovery@pm-claude-skills"
+echo "  /plugin install pm-planning@pm-claude-skills"
+echo "  /plugin install pm-delivery@pm-claude-skills"
+echo "  /plugin install pm-analytics@pm-claude-skills"
+echo "  /plugin install pm-strategy@pm-claude-skills"
+echo "  /plugin install pm-advanced@pm-claude-skills"
+echo "  /plugin install pm-rituals@pm-claude-skills"
+echo ""
+echo "=== Done ==="
@@ -0,0 +1,180 @@
+#!/bin/bash
+
+# =============================================================================
+# create-plugin-jsons.sh
+# Run this from the ROOT of your pm-claude-skills repo.
+# Creates .claude-plugin/plugin.json inside each of the 6 new plugin folders.
+# Your skills/ subfolders are already in place — this just adds the missing
+# plugin.json files.
+# =============================================================================
+
+set -e
+
+REPO_ROOT="$(pwd)"
+
+echo "================================================"
+echo " pm-claude-skills — Creating plugin.json files"
+echo " Running from: $REPO_ROOT"
+echo "================================================"
+echo ""
+
+# Sanity check — make sure we're in the right place
+if [ ! -d "$REPO_ROOT/pm-gtm" ] || [ ! -d "$REPO_ROOT/pm-engineering" ]; then
+  echo "ERROR: Cannot find pm-gtm or pm-engineering folders."
+  echo "Make sure you are running this from the ROOT of your pm-claude-skills repo."
+  echo "Example: cd ~/pm-claude-skills && bash create-plugin-jsons.sh"
+  exit 1
+fi
+
+# ---------------------------------------------------------
+# BUNDLE 1: pm-gtm
+# ---------------------------------------------------------
+echo "Creating pm-gtm/.claude-plugin/plugin.json..."
+mkdir -p pm-gtm/.claude-plugin
+cat > pm-gtm/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-gtm",
+  "version": "1.0.0",
+  "description": "Marketing & GTM skills: Go-To-Market Planner, Content Calendar, Competitor Teardown, Email Campaign. Build positioning statements, messaging pillars, feature lists, use cases, and launch campaigns.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "marketing", "gtm", "positioning", "content-calendar", "competitor-analysis", "email-campaign"]
+}
+EOF
+echo "  ✓ pm-gtm/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 2: pm-engineering
+# ---------------------------------------------------------
+echo "Creating pm-engineering/.claude-plugin/plugin.json..."
+mkdir -p pm-engineering/.claude-plugin
+cat > pm-engineering/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-engineering",
+  "version": "1.0.0",
+  "description": "Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record. Structured outputs for engineering teams and technical PMs.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "engineering", "code-review", "incident-postmortem", "api-documentation", "adr", "architecture"]
+}
+EOF
+echo "  ✓ pm-engineering/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 3: pm-data
+# ---------------------------------------------------------
+echo "Creating pm-data/.claude-plugin/plugin.json..."
+mkdir -p pm-data/.claude-plugin
+cat > pm-data/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-data",
+  "version": "1.0.0",
+  "description": "Data & analytics skills: Metrics Framework, SQL Query Explainer, Dashboard Brief. Build North Star metric trees, explain and optimise SQL, and spec dashboards from business questions.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "data", "analytics", "metrics", "north-star", "sql", "dashboard", "kpi"]
+}
+EOF
+echo "  ✓ pm-data/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 4: pm-people
+# ---------------------------------------------------------
+echo "Creating pm-people/.claude-plugin/plugin.json..."
+mkdir -p pm-people/.claude-plugin
+cat > pm-people/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-people",
+  "version": "1.0.0",
+  "description": "Leadership & people skills: Performance Review, Hiring Rubric, Team Offsite Planner. Write structured reviews, build interview scorecards, and plan offsites from goals to minute-by-minute agenda.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "leadership", "management", "performance-review", "hiring", "interview", "offsite", "people"]
+}
+EOF
+echo "  ✓ pm-people/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 5: pm-design
+# ---------------------------------------------------------
+echo "Creating pm-design/.claude-plugin/plugin.json..."
+mkdir -p pm-design/.claude-plugin
+cat > pm-design/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-design",
+  "version": "1.0.0",
+  "description": "Design & UX skills: UX Research Plan, Design Critique, Accessibility Audit. Create research plans with discussion guides, critique designs using JTBD and Gestalt principles, and audit for WCAG 2.2 compliance.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "design", "ux", "user-research", "accessibility", "wcag", "usability", "design-critique"]
+}
+EOF
+echo "  ✓ pm-design/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 6: pm-business
+# ---------------------------------------------------------
+echo "Creating pm-business/.claude-plugin/plugin.json..."
+mkdir -p pm-business/.claude-plugin
+cat > pm-business/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-business",
+  "version": "1.0.0",
+  "description": "Business & strategy skills: Investor Update, Board Deck Narrative, Job Application. Write investor updates investors actually read, structure board presentations, and tailor CVs and cover letters with ATS optimisation.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "business", "strategy", "investor-update", "board-deck", "startup", "career", "job-application"]
+}
+EOF
+echo "  ✓ pm-business/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# DONE
+# ---------------------------------------------------------
+echo ""
+echo "================================================"
+echo " All 6 plugin.json files created successfully!"
+echo ""
+echo "  pm-gtm/.claude-plugin/plugin.json"
+echo "  pm-engineering/.claude-plugin/plugin.json"
+echo "  pm-data/.claude-plugin/plugin.json"
+echo "  pm-people/.claude-plugin/plugin.json"
+echo "  pm-design/.claude-plugin/plugin.json"
+echo "  pm-business/.claude-plugin/plugin.json"
+echo ""
+echo " Next steps:"
+echo "  1. bash add-plugin-json.sh   (update marketplace.json)"
+echo "  2. git add ."
+echo "  3. git commit -m 'feat: add 6 new plugin bundles (pm-gtm, pm-engineering, pm-data, pm-people, pm-design, pm-business)'"
+echo "  4. git push origin main"
+echo "================================================"
@@ -0,0 +1,180 @@
+#!/bin/bash
+
+# =============================================================================
+# create-plugin-jsons.sh
+# Run this from the ROOT of your pm-claude-skills repo.
+# Creates .claude-plugin/plugin.json inside each of the 6 new plugin folders.
+# Your skills/ subfolders are already in place — this just adds the missing
+# plugin.json files.
+# =============================================================================
+
+set -e
+
+REPO_ROOT="$(pwd)"
+
+echo "================================================"
+echo " pm-claude-skills — Creating plugin.json files"
+echo " Running from: $REPO_ROOT"
+echo "================================================"
+echo ""
+
+# Sanity check — make sure we're in the right place
+if [ ! -d "$REPO_ROOT/pm-gtm" ] || [ ! -d "$REPO_ROOT/pm-engineering" ]; then
+  echo "ERROR: Cannot find pm-gtm or pm-engineering folders."
+  echo "Make sure you are running this from the ROOT of your pm-claude-skills repo."
+  echo "Example: cd ~/pm-claude-skills && bash create-plugin-jsons.sh"
+  exit 1
+fi
+
+# ---------------------------------------------------------
+# BUNDLE 1: pm-gtm
+# ---------------------------------------------------------
+echo "Creating pm-gtm/.claude-plugin/plugin.json..."
+mkdir -p pm-gtm/.claude-plugin
+cat > pm-gtm/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-gtm",
+  "version": "1.0.0",
+  "description": "Marketing & GTM skills: Go-To-Market Planner, Content Calendar, Competitor Teardown, Email Campaign. Build positioning statements, messaging pillars, feature lists, use cases, and launch campaigns.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "marketing", "gtm", "positioning", "content-calendar", "competitor-analysis", "email-campaign"]
+}
+EOF
+echo "  ✓ pm-gtm/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 2: pm-engineering
+# ---------------------------------------------------------
+echo "Creating pm-engineering/.claude-plugin/plugin.json..."
+mkdir -p pm-engineering/.claude-plugin
+cat > pm-engineering/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-engineering",
+  "version": "1.0.0",
+  "description": "Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record. Structured outputs for engineering teams and technical PMs.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "engineering", "code-review", "incident-postmortem", "api-documentation", "adr", "architecture"]
+}
+EOF
+echo "  ✓ pm-engineering/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 3: pm-data
+# ---------------------------------------------------------
+echo "Creating pm-data/.claude-plugin/plugin.json..."
+mkdir -p pm-data/.claude-plugin
+cat > pm-data/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-data",
+  "version": "1.0.0",
+  "description": "Data & analytics skills: Metrics Framework, SQL Query Explainer, Dashboard Brief. Build North Star metric trees, explain and optimise SQL, and spec dashboards from business questions.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "data", "analytics", "metrics", "north-star", "sql", "dashboard", "kpi"]
+}
+EOF
+echo "  ✓ pm-data/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 4: pm-people
+# ---------------------------------------------------------
+echo "Creating pm-people/.claude-plugin/plugin.json..."
+mkdir -p pm-people/.claude-plugin
+cat > pm-people/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-people",
+  "version": "1.0.0",
+  "description": "Leadership & people skills: Performance Review, Hiring Rubric, Team Offsite Planner. Write structured reviews, build interview scorecards, and plan offsites from goals to minute-by-minute agenda.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "leadership", "management", "performance-review", "hiring", "interview", "offsite", "people"]
+}
+EOF
+echo "  ✓ pm-people/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 5: pm-design
+# ---------------------------------------------------------
+echo "Creating pm-design/.claude-plugin/plugin.json..."
+mkdir -p pm-design/.claude-plugin
+cat > pm-design/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-design",
+  "version": "1.0.0",
+  "description": "Design & UX skills: UX Research Plan, Design Critique, Accessibility Audit. Create research plans with discussion guides, critique designs using JTBD and Gestalt principles, and audit for WCAG 2.2 compliance.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "design", "ux", "user-research", "accessibility", "wcag", "usability", "design-critique"]
+}
+EOF
+echo "  ✓ pm-design/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# BUNDLE 6: pm-business
+# ---------------------------------------------------------
+echo "Creating pm-business/.claude-plugin/plugin.json..."
+mkdir -p pm-business/.claude-plugin
+cat > pm-business/.claude-plugin/plugin.json << 'EOF'
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-business",
+  "version": "1.0.0",
+  "description": "Business & strategy skills: Investor Update, Board Deck Narrative, Job Application. Write investor updates investors actually read, structure board presentations, and tailor CVs and cover letters with ATS optimisation.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "business", "strategy", "investor-update", "board-deck", "startup", "career", "job-application"]
+}
+EOF
+echo "  ✓ pm-business/.claude-plugin/plugin.json created"
+
+# ---------------------------------------------------------
+# DONE
+# ---------------------------------------------------------
+echo ""
+echo "================================================"
+echo " All 6 plugin.json files created successfully!"
+echo ""
+echo "  pm-gtm/.claude-plugin/plugin.json"
+echo "  pm-engineering/.claude-plugin/plugin.json"
+echo "  pm-data/.claude-plugin/plugin.json"
+echo "  pm-people/.claude-plugin/plugin.json"
+echo "  pm-design/.claude-plugin/plugin.json"
+echo "  pm-business/.claude-plugin/plugin.json"
+echo ""
+echo " Next steps:"
+echo "  1. bash add-plugin-json.sh   (update marketplace.json)"
+echo "  2. git add ."
+echo "  3. git commit -m 'feat: add 6 new plugin bundles (pm-gtm, pm-engineering, pm-data, pm-people, pm-design, pm-business)'"
+echo "  4. git push origin main"
+echo "================================================"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-advanced",
+  "version": "3.0.0",
+  "description": "Advanced PM skills: AI Product Canvas, Multi-Source Signal Synthesiser, Experiment Designer, Design Handoff Brief. For senior PMs working on complex or AI-powered products.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "ai-product", "experiment-design", "design-handoff", "signal-synthesis"]
+}
@@ -0,0 +1,145 @@
+---
+name: ai-product-canvas
+description: Structures AI and ML product decisions including model selection, data requirements, evaluation frameworks, and responsible AI considerations. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Triggers on "AI product", "LLM feature", "AI canvas", "build with AI", "AI integration", "AI-powered", "machine learning feature".
+---
+
+# AI Product Canvas Skill
+
+Define AI products with the same rigour as any product decision — but with additional layers for data, model, evaluation, and responsible AI. This canvas prevents the most common AI product failure: building a technically impressive feature that doesn't solve a real problem.
+
+## AI Product Anti-Patterns to Check First
+
+Before building, flag if any of these apply:
+- ❌ "We should add AI to [existing feature]" — with no user problem defined
+- ❌ Accuracy target undefined before build begins
+- ❌ No plan for what happens when the model is wrong
+- ❌ User-facing AI output with no human review or fallback
+- ❌ Training data not audited for bias or quality
+- ❌ No evaluation metric — "we'll know it when we see it"
+
+---
+
+## AI Product Canvas Output Format
+
+### AI Product Canvas — [Feature Name] — [Date]
+
+**PM Owner:** [Name]
+**ML/AI Lead:** [Name]
+**Status:** Discovery / Design / Build / Evaluation / Live
+
+---
+
+#### 1. Problem Definition
+**User problem being solved:**
+> [What specific situation is the user in? What job are they trying to get done?]
+
+**Why AI?**
+> [What makes this problem require AI vs a deterministic solution? If the answer is "because we can," stop here.]
+
+**Success for the user looks like:**
+> [What outcome does the user experience when the AI feature is working well?]
+
+---
+
+#### 2. AI Approach
+
+**Task type:**
+- [ ] Classification
+- [ ] Generation (text, image, code)
+- [ ] Summarisation / extraction
+- [ ] Recommendation
+- [ ] Search / retrieval
+- [ ] Prediction / forecasting
+- [ ] Conversation / agent
+
+**Model approach:**
+- [ ] LLM API (GPT-4, Claude, Gemini, etc.) — specify: [Model name + version]
+- [ ] Fine-tuned model on own data
+- [ ] Custom model trained from scratch
+- [ ] RAG (retrieval-augmented generation)
+- [ ] Embedding + vector search
+
+**Rationale for chosen approach:** [Why this, not alternatives]
+
+---
+
+#### 3. Data Requirements
+
+| Data Type | Source | Volume | Quality Status | Bias Risk |
+|---|---|---|---|---|
+| [Training data] | [Where it comes from] | [Volume] | [Audit status] | H/M/L |
+| [Evaluation data] | [Where it comes from] | [Volume] | [Audit status] | H/M/L |
+
+**Data gaps:** [What's missing and plan to get it]
+**Privacy considerations:** [Any PII in training or inference data]
+**Data ownership:** [Do we own this data? Can we use it for training?]
+
+---
+
+#### 4. Evaluation Framework
+
+**Primary metric:** [The number that defines success — accuracy, F1, BLEU, user rating, task completion rate]
+**Minimum acceptable threshold:** [Below X, the feature does not ship]
+**Human evaluation plan:** [How will humans review model outputs? Sampling rate? Review panel?]
+
+| Evaluation Type | Method | Cadence | Owner |
+|---|---|---|---|
+| Offline (pre-launch) | [Test set, benchmark] | Pre-launch | ML Lead |
+| Online (post-launch) | [A/B test, user feedback] | Weekly | PM + ML |
+| Adversarial | [Red-team, edge cases] | Pre-launch | Safety reviewer |
+
+---
+
+#### 5. User Experience Design
+
+**How is AI output presented?**
+- [ ] Direct output shown to user (high trust required)
+- [ ] AI-assisted with user confirmation
+- [ ] Suggestion user can accept/reject
+- [ ] Background action with audit log
+
+**Confidence and uncertainty handling:**
+- What happens when confidence is low? [Show alternative, ask for clarification, fallback to manual]
+- How is uncertainty communicated to the user? [UI pattern]
+
+**Fallback plan:**
+- If the model fails or returns an error: [Specific fallback behaviour]
+- If accuracy degrades below threshold: [Kill switch or graceful degradation plan]
+
+---
+
+#### 6. Responsible AI Checklist
+
+- [ ] Bias audit completed on training data
+- [ ] Demographic fairness evaluated (does performance differ by user group?)
+- [ ] Hallucination / confabulation risk assessed and mitigated
+- [ ] User can see and correct AI output
+- [ ] Opt-out mechanism exists (can user disable the AI feature?)
+- [ ] Output provenance visible when relevant (does user know AI generated this?)
+- [ ] PII not used in ways user didn't consent to
+- [ ] Regulatory review completed (GDPR, AI Act, sector-specific)
+- [ ] Model cards / documentation completed
+
+---
+
+#### 7. Launch & Monitoring Plan
+
+**Rollout:** [% of users, with staged expansion criteria]
+**Monitoring metrics:**
+- Model performance: [Metric + alert threshold]
+- User engagement with AI output: [Acceptance rate, override rate, feedback score]
+- Error rate: [% of failed inferences]
+- Latency: [P95 target]
+
+**Model refresh cadence:** [How often is the model retrained or updated?]
+**Drift detection:** [How will you know when model performance degrades in production?]
+
+---
+
+## Guidelines
+
+- Never skip the "Why AI?" section — it's the most important question in AI product development
+- The fallback UX is not optional — what happens when AI fails defines your product's trustworthiness
+- Responsible AI checklist must be completed before launch, not after
+- Include latency in success metrics — a 5-second AI response is often worse than no AI at all
+- Recommend starting with a human-in-the-loop design and automating only when accuracy is proven
@@ -0,0 +1,59 @@
+---
+name: design-handoff-brief
+description: Transform feature briefs into structured design briefs that give designers the context they need
+tool_integration: Figma, Notion
+---
+# Design Handoff Brief Skill
+
+## Purpose
+Produce a design brief that sets designers up for success — grounding them in user context and constraints before they open Figma, not after they've gone in the wrong direction.
+
+## What Designers Actually Need (and PMs Often Skip)
+- The user's goal, not the feature name
+- The emotional state of the user at this moment in the journey
+- What success looks like — how will we know the design worked?
+- Constraints: technical, legal, brand, accessibility
+- Edge cases that must be handled
+- What we're explicitly NOT solving for
+
+## Process
+1. Read the feature brief or PRD provided
+2. Extract user goal (reframe from feature language to user outcome language)
+3. Identify constraints — technical limitations, brand guidelines, accessibility requirements
+4. List edge cases the design must handle
+5. Define success criteria the design should be evaluated against
+6. Write a "not in scope" section to prevent scope creep in design
+
+## Output Format
+
+### Design Brief: [Feature Name]
+
+**User Goal:** (in the user's words, not ours)
+"When I [situation], I want to [motivation] so that I can [outcome]."
+
+**Context & Emotional State:**
+[Where is the user in their journey? What are they feeling? What just happened?]
+
+**Design Success Criteria:**
+- [Criterion 1 — measurable where possible]
+- [Criterion 2]
+- [Criterion 3]
+
+**Constraints:**
+- Technical: [limitations engineering has flagged]
+- Brand: [relevant brand guidelines]
+- Accessibility: [WCAG level required, any specific requirements]
+- Legal/Compliance: [if applicable]
+
+**Edge Cases to Design For:**
+- [Edge case 1]
+- [Edge case 2]
+- [Edge case 3]
+
+**Explicitly Out of Scope:**
+- [What we are NOT solving in this design iteration]
+
+**Reference Material:**
+- User research: [link]
+- Existing patterns: [Figma component library link]
+- Competitor examples: [links if relevant]
@@ -0,0 +1,55 @@
+---
+name: experiment-designer
+description: Designs A/B tests from hypotheses and interprets experiment results 
+with statistical rigour. Use when user says "run an experiment", "design an A/B 
+test", "test this feature", "interpret these results", "was this experiment 
+successful", or "what sample size do I need".
+metadata:
+  author: Mohit Aggarwal
+  version: 1.0.0
+  category: data-and-metrics
+  tags: [experimentation, data, analytics, ab-testing]
+  documentation: https://github.com/mohitagw15856/pm-claude-skills
+---
+# Experiment Designer Skill
+
+## Purpose
+Produce rigorous experiment designs from product hypotheses, and interpret 
+results with statistical and practical significance — so you can defend every 
+decision to a sceptical engineering lead or data scientist.
+
+## Two-Phase Process
+
+### Phase 1: Experiment Design
+**Required inputs:** hypothesis, primary metric, current baseline, minimum 
+detectable effect (MDE), available sample size per day.
+
+**Output:**
+- Hypothesis restated as: "If we [change], we expect [metric] to [move by X%] 
+  because [reason]"
+- Control and variant definitions
+- Primary metric (one only)
+- Secondary guardrail metrics (2-3 max)
+- Required sample size (calculated from MDE and baseline)
+- Estimated run time in days
+- Pre-defined success criteria (before the test runs — no moving goalposts)
+- Design risk flags: novelty effects, seasonal confounds, multiple testing issues,
+  network effects, sample ratio mismatch risks
+
+### Phase 2: Results Interpretation
+**Required inputs:** control results, variant results, p-value or raw numbers, 
+run duration, any anomalies observed.
+
+**Output:**
+- Statistical significance assessment (p < 0.05 threshold)
+- Practical significance: was the lift meaningful for the business, not just real?
+- Confidence interval interpretation
+- Confounding factors to investigate
+- Recommendation: Ship / Iterate / Kill / Run follow-up test
+- If "Iterate": specific hypotheses to test next
+
+## Quality Checks
+- Never interpret results from an underpowered test without flagging it
+- Always distinguish statistical from practical significance
+- Flag if test was stopped early (peeking problem)
+- Note if sample ratio mismatch occurred
@@ -0,0 +1,62 @@
+---
+name: multi-source-signal-synthesiser
+description: Synthesises user signals from multiple research sources into a 
+unified insight brief, reconciling conflicting feedback. Use when user has data 
+from multiple sources, needs to "make sense of all this user data", "what are 
+users really telling us", "synthesise our research", or has conflicting feedback 
+from different channels.
+metadata:
+  author: Mohit Aggarwal
+  version: 1.0.0
+  category: discovery
+  tags: [user-research, synthesis, discovery, insights]
+  documentation: https://github.com/mohitagw15856/pm-claude-skills
+---
+# Multi-Source Signal Synthesiser Skill
+
+## Purpose
+Reconcile user signals from multiple sources — interviews, support tickets, NPS, 
+app reviews, sales calls — into a unified, weighted insight brief that surfaces 
+the underlying need rather than the surface-level request.
+
+## Source Weighting (default — adapt to your context)
+- Direct research (interviews, usability tests): weight 5
+- Support tickets (unprompted pain signals): weight 4
+- NPS verbatims: weight 3
+- App store reviews: weight 2
+- Sales call summaries (filtered through sales lens): weight 2
+- Anecdote or single report: weight 1
+
+## Process
+1. Accept inputs from any combination of the source types above
+2. Tag each signal by source and apply weight
+3. Look for CONVERGENCE: same underlying need appearing across 3+ sources
+4. Look for DIVERGENCE: contradictory signals suggesting user segmentation
+5. Distinguish surface request from underlying need
+   (e.g. "faster export" may mean "I don't trust the data will be there when 
+   I need it")
+6. Produce ranked insights by weighted frequency
+
+## Output Format
+
+### User Signal Synthesis — [Date / Period]
+**Sources included:** [list]
+**Total signals processed:** [n]
+
+#### Insight 1: [Underlying need, not feature request]
+- **Confidence:** High / Medium / Low (based on source diversity and weight)
+- **Evidence:** [Signals from each source supporting this]
+- **Conflicting signals:** [Any contradicting evidence and how to interpret it]
+- **Product implication:** [Specific, not generic]
+
+[Repeat for top 3-5 insights]
+
+#### Divergent Signals (Possible Segmentation)
+[Where user groups appear to have genuinely different needs]
+
+#### What the Data Does NOT Tell Us
+[Gaps that require further research before acting]
+
+## OpenClaw Configuration
+Connect to: Notion (research docs), support inbox, NPS tool, app review feed.
+Schedule: weekly synthesis run, diff output showing new signals only.
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-analytics",
+  "version": "3.0.0",
+  "description": "Data & metrics skills: Data Analysis Standard, Retention Analysis, Product Health Analysis. Structure metric deep-dives, funnel analysis, cohort studies and churn investigations.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "analytics", "retention", "metrics", "funnel", "cohort", "churn"]
+}
@@ -0,0 +1,109 @@
+---
+name: data-analysis-standard
+description: Structures product data analysis, metric deep-dives, funnel analysis, and cohort studies. Use when asked to analyse product metrics, investigate a drop in conversion, build a dashboard spec, or explain data to stakeholders. Triggers on "analyse metrics", "funnel analysis", "cohort analysis", "data deep dive", "why did X drop".
+---
+
+# Data Analysis Standard Skill
+
+Turn raw numbers into product decisions. Structure every analysis with a clear question, methodology, finding, and recommended action.
+
+## Analysis Framework: The 4-Question Method
+
+Every analysis starts here:
+1. **What changed?** (describe the metric and its movement)
+2. **Why did it change?** (root cause — segment, funnel step, cohort, channel)
+3. **So what?** (business or product impact)
+4. **Now what?** (recommended action with confidence level)
+
+Never deliver data without answering all four. A chart with no narrative is not an analysis.
+
+---
+
+## Metric Triage Template
+
+Use when a metric has moved unexpectedly:
+
+```
+METRIC: [Name]
+MOVEMENT: [X% change over Y period]
+BASELINE: [What was normal]
+
+SEGMENTATION CHECK:
+- By platform (iOS / Android / Web)?
+- By user cohort (new / returning / power users)?
+- By acquisition channel?
+- By geography?
+- By plan/tier?
+
+ROOT CAUSE HYPOTHESIS:
+1. [Most likely explanation] — Evidence: [data point]
+2. [Alternative explanation] — Evidence: [data point]
+3. [Ruling out] — Eliminated because: [reason]
+
+CONCLUSION: [Single sentence answer to "why did this change?"]
+CONFIDENCE: [High / Medium / Low] — based on [data available]
+```
+
+---
+
+## Funnel Analysis Structure
+
+| Stage | Metric | Current | Benchmark/Target | Drop-off % | Notes |
+|---|---|---|---|---|---|
+| [Top of funnel] | [Users] | [N] | [N] | — | |
+| [Step 2] | [Users] | [N] | [N] | [X%] | |
+| [Step 3] | [Users] | [N] | [N] | [X%] | |
+| [Conversion] | [Users] | [N] | [N] | [X%] | |
+
+**Biggest drop-off:** [Step X → Step Y] — Hypothesis: [reason]
+**Recommended investigation:** [specific query or test]
+
+---
+
+## Cohort Analysis Guidelines
+
+Always define:
+- **Cohort definition:** [What groups users — signup week, first action, plan type]
+- **Retention metric:** [What counts as retained — login, core action, revenue]
+- **Retention window:** [D1, D7, D30, W4, M3, etc.]
+
+Output a cohort retention table and annotate:
+- Baseline retention for each cohort
+- Cohorts that over/underperform and why (feature launch? campaign? seasonal?)
+- Trend direction across cohorts (improving / declining / stable)
+
+---
+
+## Stakeholder Analysis Output Format
+
+### [Analysis Title] — [Date]
+
+**Question being answered:** [Specific question in plain English]
+**Time period:** [Date range]
+**Data source:** [Where data comes from]
+
+**Finding:**
+> [1–2 sentence plain-English summary of what the data shows]
+
+**Key chart / table:** [Include or describe]
+
+**Root cause:** [Best explanation with evidence]
+
+**Confidence level:** [High / Medium / Low] — [reason]
+
+**Recommended action:**
+1. [Immediate action — owner, timeline]
+2. [Investigation needed — what to check next]
+3. [Monitoring — what metric to watch and at what cadence]
+
+**What this analysis does NOT tell us:** [Important caveat — what data is missing or what can't be concluded]
+
+---
+
+## Guidelines
+
+- Always state what the data *cannot* tell you — never oversell confidence
+- Correlations are not causation — flag this every time
+- If the user has no baseline, recommend establishing one before drawing conclusions
+- Recommend the simplest chart for each finding: bar for comparison, line for trends, scatter for correlation, table for detailed breakdowns
+- Always specify the time window — "conversion dropped" is meaningless without "from X to Y over Z period"
@@ -0,0 +1,43 @@
+---
+name: product-health-analysis
+description: Interpret product metrics against goals and surface actionable signals
+tool_integration: Google Analytics, Mixpanel
+---
+# Product Health Dashboard Skill
+
+## Purpose
+Transform raw metrics data into a clear health narrative — what's working, what's not, and what needs immediate attention.
+
+## Metrics Framework
+Analyse across four layers:
+1. **Acquisition** — new users, source quality, CAC trends
+2. **Activation** — time to first value, onboarding completion rates
+3. **Engagement** — DAU/MAU, feature adoption, session depth
+4. **Retention** — D1/D7/D30 retention, churn rate, resurrection rate
+
+## Process
+1. For each metric, compare: current period vs. previous period, current vs. target
+2. Flag anything more than 10% off target as requiring investigation
+3. Look for correlations — does a drop in activation explain a retention dip 2 weeks later?
+4. Write a plain-English health summary (no jargon) suitable for sharing with non-data stakeholders
+5. Recommend top 3 areas for immediate investigation with suggested diagnostic steps
+
+## Output Format
+
+### Product Health Report — [Period]
+**Overall Health:** 🟢 On Track / 🟡 Watch / 🔴 Action Required
+
+| Metric | Current | Target | vs. Last Period | Status |
+|--------|---------|--------|-----------------|--------|
+| [metric] | [value] | [target] | [+/-%] | [🟢/🟡/🔴] |
+
+**Key Observations:**
+[3-5 bullet observations written in plain English]
+
+**Areas Requiring Investigation:**
+1. [Metric + hypothesis + suggested diagnostic]
+2. [Metric + hypothesis + suggested diagnostic]
+3. [Metric + hypothesis + suggested diagnostic]
+
+**Recommended Actions:**
+[Specific next steps with owners and timelines]
@@ -0,0 +1,116 @@
+---
+name: retention-analysis
+description: Structures retention analysis, churn investigations, and engagement deep-dives for product teams. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Triggers on "retention analysis", "churn", "DAU/MAU", "user retention", "why are users leaving".
+---
+
+# Retention Analysis Skill
+
+Diagnose why users leave, identify what keeps them, and recommend specific, testable interventions — not vague "improve onboarding" suggestions.
+
+## Retention Fundamentals
+
+**The retention curve has two components:**
+1. **Steepness of initial drop** (D1–D7) — onboarding problem
+2. **Long-term floor level** — product-market fit indicator
+
+A product with PMF has a retention curve that flattens. If it trends to zero, you have a PMF problem, not an onboarding problem. Name this distinction explicitly.
+
+---
+
+## Retention Metrics Definitions
+
+| Metric | Formula | What It Tells You |
+|---|---|---|
+| D1 Retention | Users who return on day 2 ÷ new users day 1 | Quality of first experience |
+| D7 Retention | Users active on day 8 ÷ users who joined 7 days ago | Early habit formation |
+| D30 Retention | Users active on day 31 ÷ users who joined 30 days ago | Product-market fit signal |
+| DAU/MAU Ratio | Daily active users ÷ monthly active users | Stickiness (>20% good, >50% excellent) |
+| Churn Rate | Users lost in period ÷ users at start of period | Monthly or annual |
+| Net Revenue Retention | MRR at end of period ÷ MRR at start (same cohort) | Revenue health including expansion |
+
+---
+
+## Retention Investigation Framework
+
+### Step 1: Segment the problem
+Don't analyse "retention" — analyse retention for specific cohorts:
+- New vs returning users
+- Paid vs free
+- Acquisition channel (organic vs paid vs referral)
+- Onboarding path completed vs not
+- Feature usage (power users vs lurkers)
+
+### Step 2: Find the inflection points
+Where does the drop happen? D1? D7? Month 3?
+- D1 drop → First session experience
+- D7 drop → Habit loop not formed
+- D30 drop → Value not delivered at depth
+- Month 3+ drop → Boredom, competition, or lifecycle event
+
+### Step 3: Identify the "aha moment" correlation
+Which early behaviour predicts long-term retention?
+- Run correlation: users who did [X] in first 7 days vs 30-day retention
+- Common patterns: connected an integration, invited a teammate, completed a core action N times
+
+### Step 4: Qualify the churn
+Interview churned users — never skip this. Survey data alone is insufficient.
+- "What was the trigger that led you to cancel/stop?"
+- "What were you trying to accomplish that you couldn't?"
+- "What would need to change for you to come back?"
+
+---
+
+## Output Format
+
+### Retention Analysis — [Product/Segment] — [Date]
+
+**Question:** [Specific retention question being answered]
+**Period Analysed:** [Date range]
+**Segment:** [Which users]
+
+---
+
+**Current Retention Snapshot:**
+
+| Metric | Current | Industry Benchmark | Status |
+|---|---|---|---|
+| D1 Retention | [X%] | 25–40% | 🔴/🟡/🟢 |
+| D7 Retention | [X%] | 10–25% | 🔴/🟡/🟢 |
+| D30 Retention | [X%] | 5–15% | 🔴/🟡/🟢 |
+| DAU/MAU | [X%] | 10–20% typical | 🔴/🟡/🟢 |
+
+**Retention Curve Shape:** [Flattening / Still declining / Trending to zero]
+**PMF Signal:** [Strong / Weak / Absent — based on curve shape]
+
+---
+
+**Root Cause Hypotheses:**
+
+| Hypothesis | Evidence | Confidence | Test |
+|---|---|---|---|
+| [Cause] | [Data point] | H/M/L | [How to validate] |
+
+**"Aha Moment" Correlation:**
+Users who [specific action] in first [N] days retain at [X%] vs [Y%] for those who don't.
+
+---
+
+**Recommended Interventions:**
+
+| Intervention | Target Drop | Expected Lift | Effort | Priority |
+|---|---|---|---|---|
+| [Specific change] | D1 / D7 / D30 | [X%] | S/M/L | 1/2/3 |
+
+**Monitoring Plan:**
+- Metric to track: [X]
+- Review cadence: [Weekly / Monthly]
+- Alert threshold: [If X drops below Y, investigate immediately]
+
+---
+
+## Guidelines
+
+- Never recommend "improve onboarding" without specifying *what* to change and *why*
+- Benchmark against industry — consumer apps, SaaS, and marketplaces have very different retention norms
+- If DAU/MAU is below 5%, that's a PMF conversation, not a retention tactics conversation
+- Always recommend talking to churned users — no amount of data replaces understanding the *reason*
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-business",
+  "version": "1.0.0",
+  "description": "Business & strategy skills: Investor Update, Board Deck Narrative, Job Application. Write investor updates investors actually read, structure board presentations, and tailor CVs and cover letters with ATS optimisation.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "business", "strategy", "investor-update", "board-deck", "startup", "career", "job-application"]
+}
@@ -0,0 +1,157 @@
+---
+name: board-deck-narrative
+description: "Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update. Produces a complete slide-by-slide structure with narrative beats, talking points, and slide content guidance."
+---
+
+# Board Deck Narrative Skill
+
+This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Company stage and context** (Seed / Series A / Growth — and where you are in the year)
+- **Board meeting type** (Regular quarterly / Annual / Special / Fundraise-related)
+- **Key themes for this meeting** (e.g. strong growth quarter / pivoting strategy / hiring challenge / fundraise update)
+- **Key metrics to feature**
+- **Decisions needed from the board** (if any)
+- **Time available** (e.g. 60 min / 90 min)
+- **Audience** (investors only / investors + independent directors / mixed)
+
+## Output Structure
+
+---
+
+# Board Deck Narrative: [Company] — [Quarter/Period]
+
+**Meeting type:** [Regular quarterly / Special]
+**Time:** [X minutes]
+**Narrative theme:** [The one-sentence story of this quarter — e.g. "We hit our revenue target, but activation is the problem we need to solve together."]
+
+---
+
+## Opening Frame (Slide 1–2)
+
+**Slide 1: Title**
+- Company name, quarter, date
+- One-sentence framing of the meeting's narrative arc
+
+**Slide 2: Agenda**
+- List of sections + time allocation
+- Flag which sections need board input vs. are informational
+
+*Presenter note: Board members are busy. Tell them in the first 2 minutes what you need from them today. It changes how they listen.*
+
+---
+
+## Business Performance (Slides 3–6, ~15 min)
+
+**Slide 3: Scorecard / KPI Dashboard**
+- Content: Key metrics vs. targets for the quarter. No more than 6 metrics.
+- Format: Traffic-light table (Green / Amber / Red against plan)
+- Narrative: [1–2 sentences — the headline story of the quarter in numbers]
+- *Don't hide reds. Boards lose trust when they discover hidden problems later.*
+
+**Slide 4: Revenue / Growth Deep Dive**
+- Content: Revenue breakdown by segment, cohort retention, growth drivers
+- Key message: [What the data shows about the health of growth]
+- Call out: [Any trend that needs board context or discussion]
+
+**Slide 5: Unit Economics**
+- Content: CAC, LTV, payback period, gross margin — vs. last quarter and vs. plan
+- Flag: Any metric moving in the wrong direction and what's causing it
+
+**Slide 6: Operational Highlights**
+- Content: 3–5 bullet points of the most significant things that happened this quarter
+- Format: Each bullet = outcome, not activity. ("Signed 3 enterprise contracts worth £400K ARR" not "Continued enterprise sales motion")
+
+---
+
+## Strategic Update (Slides 7–9, ~15 min)
+
+**Slide 7: Strategy Snapshot**
+- Content: Where you said you'd be vs. where you are against the annual plan
+- Narrative: [Honest assessment — what's on track, what's shifted and why]
+
+**Slide 8: Key Strategic Decision or Update**
+- Content: The one strategic topic that most needs board input this meeting
+- Format: Context → Options considered → Recommendation → Question for board
+- *This is the highest-value 10 minutes of the meeting. Frame it as a real question.*
+
+**Slide 9: Product & Roadmap (if relevant)**
+- Content: Top 3 product bets this quarter — what shipped, what's coming, why these bets
+- Tailored for: What the board needs to understand to support strategic decisions, not a sprint review
+
+---
+
+## People & Organisation (Slide 10, ~5 min)
+
+**Slide 10: Team Update**
+- Content: Headcount (start vs. end of quarter), key hires made, open roles, any org changes
+- Flag: Any people risks or leadership gaps the board should know about
+- *Don't skip this slide. Board members often have network value here.*
+
+---
+
+## Financial Update (Slides 11–12, ~10 min)
+
+**Slide 11: P&L Summary**
+- Content: Revenue, gross margin, opex by category, EBITDA/net burn — actual vs. budget
+- Include: Year-to-date vs. annual plan
+
+**Slide 12: Cash & Runway**
+- Content: Cash on hand, monthly burn rate, runway at current burn
+- Include: Scenario if burn increases (e.g. key hire made), scenario if growth accelerates
+- Flag immediately: If runway is < 18 months — this needs board awareness and planning
+
+---
+
+## Closing & Asks (Slides 13–14, ~10 min)
+
+**Slide 13: Priorities for Next Quarter**
+- Content: Top 3–5 priorities and what success looks like for each
+- Format: Priority | What we're doing | How we'll know it worked
+- *Keeps board accountability consistent across meetings*
+
+**Slide 14: Board Asks**
+- Content: Specific things you need from board members before next meeting
+- Format: Each ask = specific, named if possible ("Looking for an intro to [Company] — [Board member X], do you have a connection?")
+- *A board meeting without specific asks is a missed opportunity*
+
+---
+
+## Appendix (Optional)
+
+- Detailed cohort analysis
+- Competitive landscape update
+- Full P&L
+- Team org chart
+- Any supporting data referenced in the main deck
+
+*Appendix slides are available but not presented. Board members who want detail can ask.*
+
+---
+
+## Narrative Principles
+
+- **Lead with honesty.** If it was a hard quarter, say so in the first slide. Don't bury bad news after the wins.
+- **One slide = one idea.** If a slide has two messages, split it.
+- **Fewer slides, more depth.** A 14-slide deck presented well beats a 35-slide deck rushed through.
+- **Every slide has a "so what."** A slide that just shows data without a takeaway wastes board time.
+- **Leave time for discussion.** Board value is in the conversation, not the presentation. Aim to spend 40% of the meeting presenting and 60% in discussion.
+
+## Quality Checks
+
+- [ ] Opening frame states the meeting's narrative theme
+- [ ] Scorecard slide uses traffic-light format (not just green metrics)
+- [ ] Strategic decision slide frames a real question for the board
+- [ ] Financial slide includes runway explicitly
+- [ ] Board asks are specific and actionable
+- [ ] Deck is ≤ 15 slides (excluding appendix)
+
+## Example Trigger Phrases
+
+- "Build a board deck structure for our Q[N] board meeting"
+- "Help me create the narrative for our board presentation"
+- "Write the slide structure for our annual board review"
+- "Design a board deck for [specific context — e.g. fundraise update]"
@@ -0,0 +1,127 @@
+---
+name: investor-update
+description: "Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors. Produces a clear, credible update with highlights, metrics, challenges, and asks — in the format investors actually want to read."
+---
+
+# Investor Update Skill
+
+This skill writes a complete investor update — structured for clarity, honest about challenges, and specific about asks. Output follows the format preferred by most early-stage and growth investors.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Company name and stage** (Seed / Series A / Series B / etc.)
+- **Period covered** (month or quarter)
+- **Key metrics this period** (revenue, MRR, users, churn, burn, runway — whatever's relevant)
+- **Biggest wins**
+- **Biggest challenges or misses**
+- **Specific asks from investors** (intros, advice, talent, partnerships)
+- **What's coming next period**
+- **Tone** (formal / conversational — most investors prefer conversational)
+
+## Output Structure
+
+---
+
+**[Company Name] — [Month/Quarter] Update**
+*[Date]*
+
+---
+
+Hi [Investor names or "all"],
+
+[One or two sentence opener — a specific highlight or honest framing of the period. Don't open with "Hope you're well." Open with the most important thing that happened.]
+
+---
+
+## The Numbers
+
+| Metric | This Period | Last Period | Change |
+|---|---|---|---|
+| [MRR / ARR] | [Value] | [Value] | [+/- %] |
+| [Active users / customers] | | | |
+| [Churn rate] | | | |
+| [Burn rate] | | | |
+| [Runway] | | | |
+| [Other key metric] | | | |
+
+[1–2 sentences of narrative on the numbers — what's the story behind the movement? Don't just repeat the table.]
+
+---
+
+## Highlights
+
+**[Highlight 1 — 4–6 word title]**
+[2–4 sentences. What happened. Why it matters. Be specific — name the customer, the number, the milestone.]
+
+**[Highlight 2]**
+[2–4 sentences]
+
+**[Highlight 3 — optional]**
+
+---
+
+## Challenges
+
+[This section is what separates trustworthy updates from self-promotional ones. Investors know you have challenges. Being direct builds trust.]
+
+**[Challenge 1]**
+[2–4 sentences. What the problem is. What you've tried. What you're doing about it. Don't spin — investors see through it.]
+
+**[Challenge 2 — if applicable]**
+
+---
+
+## Focus for Next [Month/Quarter]
+
+[3–5 bullet points. What you're concentrating on next period and why. Keep it tight — not an exhaustive roadmap.]
+
+- [Priority 1]
+- [Priority 2]
+- [Priority 3]
+
+---
+
+## Asks
+
+[Be specific. "Let me know if you can help" is not an ask. These should be actionable items an investor can act on immediately.]
+
+1. **[Ask type: e.g. Intro]** — [Specific request. e.g. "Looking for an intro to procurement leads at mid-market SaaS companies. Happy to share a warm intro note."]
+2. **[Ask type: e.g. Advice]** — [Specific question you want input on]
+3. **[Ask type: e.g. Talent]** — [Specific hire you're looking for — title, key requirements]
+
+---
+
+[Closing line — 1 sentence. Forward-looking or a genuine thanks. Not "as always, let me know if you have questions."]
+
+[Signature]
+[Name]
+[Company]
+[One way to reply — email / Calendly / reply to this thread]
+
+---
+
+## Writing Rules
+
+- Updates should take an investor 3–4 minutes to read. If it's longer, trim it.
+- Never lead with process ("This month we focused on...") — lead with outcomes
+- Challenges section must be honest. A missing challenges section signals the founder isn't self-aware or isn't being transparent.
+- Metrics table must include comparison to last period — a number without context is meaningless
+- Asks must be specific enough that an investor knows within 5 seconds if they can help
+- No jargon or buzzwords ("synergies," "crushing it," "hockey stick") — plain language only
+
+## Quality Checks
+
+- [ ] Opens with a specific highlight or honest framing (not a pleasantry)
+- [ ] Numbers include period-over-period comparison
+- [ ] Challenges section is present and honest
+- [ ] Asks are specific and actionable
+- [ ] Total length is skimmable in 3–4 minutes
+- [ ] No spin or buzzwords
+
+## Example Trigger Phrases
+
+- "Write an investor update for [month/quarter]"
+- "Draft a monthly update for our investors based on these notes: [paste notes]"
+- "Help me write a board update for Q[N]"
+- "Write our Series A investor newsletter"
@@ -0,0 +1,128 @@
+---
+name: job-application
+description: "Tailor a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter."
+---
+
+# Job Application Skill
+
+This skill tailors a CV and cover letter to a specific job description — optimising for ATS keyword matching while keeping the writing human and compelling. It also flags gaps between the candidate's profile and the role requirements.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Job description** (paste in full)
+- **Current CV / resume** (paste or describe key experience, roles, and skills)
+- **The specific thing that excites them about this role** (used in the cover letter — must be genuine)
+- **Any particular strengths to emphasise** (optional)
+- **Any gaps they're worried about** (optional — helps address them proactively)
+
+## Output Structure
+
+---
+
+## Part 1: JD Analysis
+
+Before writing anything, analyse the job description and output:
+
+### Must-Have Requirements
+[List explicit requirements from the JD — qualifications, years of experience, specific skills]
+
+### Key Themes in the JD
+[3–5 themes that repeat or are emphasised — these are the keywords and priorities the hiring manager cares about most]
+
+### ATS Keywords to Include
+[List 10–15 specific keywords and phrases from the JD that should appear in the CV and cover letter. Include: tools, methodologies, job titles, skills]
+
+### Gaps Assessment
+[Honest comparison between the candidate's profile and the JD requirements. Flag: "Strong match" / "Partial match — can be positioned as X" / "Gap — address in cover letter or don't apply"]
+
+---
+
+## Part 2: Tailored CV Summary / Profile Section
+
+Rewrite or create the candidate's CV summary/profile section (the 3–5 lines at the top of a CV) specifically for this role:
+
+**Rules:**
+- Open with the job title or a near-match (ATS reward)
+- Include 2–3 keywords from the JD naturally
+- Reference years of experience in the relevant area
+- End with a forward-looking line connecting their background to what this role needs
+- Keep to 60–80 words maximum
+
+**Tailored CV Summary:**
+[Write the summary]
+
+---
+
+## Part 3: Experience Bullet Point Rewrites
+
+For the 2–3 most relevant roles on the CV, suggest how to reframe existing bullet points to better match this JD:
+
+**[Role Title] at [Company]**
+
+| Original Bullet | Tailored Version | Why |
+|---|---|---|
+| [Candidate's original text] | [Improved version with JD keywords and stronger impact framing] | [Brief note on what changed] |
+
+**Rules for bullet point rewrites:**
+- Lead with an action verb
+- Include a quantified outcome where possible (%, £, time saved, users impacted)
+- Weave in JD keywords naturally — not forced
+- Keep to one line (2 max)
+
+---
+
+## Part 4: Cover Letter
+
+**Format:** 3 paragraphs + closing. Target: 250–350 words. Anything longer won't be read.
+
+---
+
+[Hiring Manager's name if known, otherwise "Hiring Team"]
+
+**Paragraph 1 — The Hook (Why this role, specifically)**
+[2–4 sentences. Reference something specific about the company or role — not generic enthusiasm. The candidate's genuine reason for applying goes here. This is what makes it human. Generic openers like "I am writing to apply for..." are filtered out mentally within 3 seconds.]
+
+**Paragraph 2 — The Evidence (Why them)**
+[3–5 sentences. 2–3 specific examples from their background that directly address the JD's key themes. Use the language of the JD. Include at least one quantified achievement. Don't list everything — pick the 2–3 strongest matches and go deep, not broad.]
+
+**Paragraph 3 — The Forward Bridge (Why now)**
+[2–3 sentences. Connect their trajectory to this role. Why is this the logical next step? What do they want to learn or build that this role enables? This should feel like the natural continuation of their career, not just "I want a new challenge."]
+
+---
+
+I'd welcome the chance to discuss how my background could contribute to [Company/Team]. Thank you for your time.
+
+[Name]
+[Email] | [LinkedIn URL] | [Location if relevant]
+
+---
+
+## Part 5: Application Checklist
+
+Before submitting:
+- [ ] CV summary updated with tailored version above
+- [ ] ATS keywords appear in CV body (not just summary)
+- [ ] Cover letter is under 400 words
+- [ ] Company name is spelled correctly throughout (sounds obvious — it happens)
+- [ ] No generic phrases: "passionate about," "results-driven," "team player" without evidence
+- [ ] LinkedIn profile updated to match CV (recruiters cross-check)
+- [ ] Role title in subject line if emailing directly
+
+---
+
+## Quality Checks
+
+- [ ] JD analysis completed before writing (not skipped)
+- [ ] ATS keywords are integrated naturally (not stuffed)
+- [ ] Cover letter opens with something specific (not a generic opener)
+- [ ] Paragraph 2 includes at least one quantified achievement
+- [ ] Cover letter is 250–350 words
+- [ ] Gaps are either addressed or strategically omitted
+
+## Example Trigger Phrases
+
+- "Help me apply for this job: [paste JD]"
+- "Tailor my CV for this role: [paste JD + CV]"
+- "Write a cover letter for [role] at [company]"
+- "Optimise my application for ATS for this job description"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-data",
+  "version": "1.0.0",
+  "description": "Data & analytics skills: Metrics Framework, SQL Query Explainer, Dashboard Brief. Build North Star metric trees, explain and optimise SQL, and spec dashboards from business questions.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "data", "analytics", "metrics", "north-star", "sql", "dashboard", "kpi"]
+}
@@ -0,0 +1,122 @@
+---
+name: dashboard-brief
+description: "Convert a business question into a complete dashboard specification. Use when asked to design a dashboard, create a dashboard spec or brief, plan a BI report, or define what charts and metrics a dashboard should include. Produces a structured spec with metrics, dimensions, chart types, filters, and layout guidance."
+---
+
+# Dashboard Brief Skill
+
+This skill converts a business question or monitoring need into a complete, implementation-ready dashboard specification. The output gives a data engineer or BI developer everything they need to build without a follow-up meeting.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **The business question this dashboard should answer** (e.g. "How is our activation funnel performing this week?")
+- **Primary audience** (exec / product team / operations / customer success / engineering)
+- **Refresh cadence** (real-time / hourly / daily / weekly)
+- **Data sources available** (e.g. Postgres, BigQuery, Mixpanel, Salesforce, Jira)
+- **BI tool being used** (Looker / Metabase / Tableau / Power BI / Grafana / Custom / Unknown)
+
+## Output Structure
+
+---
+
+# Dashboard Brief: [Dashboard Name]
+
+**Business Question:** [The question this dashboard answers — verbatim from inputs or refined]
+**Audience:** [Who uses this]
+**Refresh Rate:** [Real-time / Hourly / Daily / Weekly]
+**Data Sources:** [List]
+**BI Tool:** [Tool or Unknown]
+
+---
+
+## Section 1: Key Metrics (KPI Cards)
+
+List the headline numbers that should appear at the top of the dashboard as KPI cards.
+
+| Metric | Definition | Data Source | Comparison |
+|---|---|---|---|
+| [Metric name] | [How it's calculated] | [Table/source] | [vs. last week / vs. target / MoM] |
+
+Aim for 3–6 KPI cards. More than 6 is noise.
+
+---
+
+## Section 2: Charts & Visualisations
+
+For each chart, specify:
+
+### Chart [N]: [Chart Title]
+
+- **Chart type:** [Line / Bar / Stacked bar / Pie / Funnel / Heatmap / Table / Scatter]
+- **Why this chart type:** [One sentence — why this type suits this data]
+- **X-axis / Rows:** [Dimension — e.g. Date, User segment, Product]
+- **Y-axis / Values:** [Metric — e.g. Count of active users, Revenue]
+- **Breakdown/colour:** [Optional secondary dimension — e.g. by Plan tier, by Channel]
+- **Data source:** [Table or source]
+- **Filters:** [Any default filters applied — e.g. "Exclude internal test accounts"]
+- **Key insight to surface:** [What pattern or signal this chart should help the viewer spot]
+
+---
+
+## Section 3: Filters & Controls
+
+Global filters available to dashboard viewers:
+
+| Filter | Type | Default | Options |
+|---|---|---|---|
+| Date range | Date picker | Last 30 days | Custom |
+| [Segment filter] | Dropdown | All | [List relevant values] |
+| [Other filter] | Multi-select | All | [List relevant values] |
+
+---
+
+## Section 4: Layout Recommendation
+
+Describe the dashboard layout in plain terms:
+
+```
+[ROW 1 — KPI Cards]: [Metric 1] | [Metric 2] | [Metric 3] | [Metric 4]
+[ROW 2 — Primary chart, full width]: [Chart name]
+[ROW 3 — Two charts side by side]: [Chart A] | [Chart B]
+[ROW 4 — Supporting table, full width]: [Table name]
+```
+
+---
+
+## Section 5: Data Requirements
+
+List any data transformations, joins, or derived fields needed:
+
+| Derived Field | Logic | Source Tables |
+|---|---|---|
+| [Field name] | [How it's calculated] | [Tables involved] |
+
+Flag any fields that may not exist in current data infrastructure.
+
+---
+
+## Section 6: Access & Ownership
+
+- **Dashboard owner:** [Leave for user to fill]
+- **Who can edit:** [Leave for user to fill]
+- **Who can view:** [Leave for user to fill]
+- **Review cadence:** [When should this dashboard be reviewed for relevance?]
+
+---
+
+## Quality Checks
+
+- [ ] Every chart has a stated "key insight to surface" — not just "show the data"
+- [ ] KPI cards are 3–6 (not more)
+- [ ] Chart types are justified
+- [ ] Layout follows visual hierarchy (summary → detail)
+- [ ] Data requirements section flags any missing fields
+- [ ] Filters are practical and don't require IT to configure
+
+## Example Trigger Phrases
+
+- "Design a dashboard to track [business process]"
+- "Give me a spec for a [team] performance dashboard"
+- "What should go on a [topic] dashboard?"
+- "Write a dashboard brief for our [metric] monitoring"
@@ -0,0 +1,103 @@
+---
+name: metrics-framework
+description: "Build a metrics framework for any product, team, or business. Use when asked for a metrics tree, KPI framework, North Star metric, AARRR funnel, HEART framework, or OKR metrics. Produces a structured metrics hierarchy from North Star down to leading indicators, with measurement guidance."
+---
+
+# Metrics Framework Skill
+
+This skill builds a complete metrics framework tailored to a product or business. It connects the North Star metric to actionable leading indicators, making it clear which metrics to track, which to optimise, and how they relate to each other.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Product or business description** (one paragraph is enough)
+- **Business model** (SaaS / Marketplace / E-commerce / Consumer app / B2B / Other)
+- **Stage** (Pre-PMF / Growth / Scale / Mature)
+- **Framework preference** (if they have one): North Star + Metric Tree / AARRR / HEART / OKRs / Custom
+- **Primary goal this quarter** (e.g. grow activation, reduce churn, increase revenue)
+
+If no framework preference is given, recommend the best fit based on stage and business model.
+
+## Output Structure
+
+### 1. Framework Recommendation (if not specified)
+
+Explain in 2–3 sentences why you're recommending this framework for their context.
+
+---
+
+### 2. North Star Metric
+
+**[Metric Name]:** [Definition — exactly what is measured and how]
+
+**Why this is the right North Star for this business:**
+[2–3 sentences. It should reflect customer value delivered, not just revenue or activity. Explain what behaviour it captures and why maximising it correlates with long-term business health.]
+
+**How to measure it:** [Formula or data source]
+**Current baseline:** [Leave as [ADD BASELINE] for user to fill]
+**Target:** [Leave as [ADD TARGET] for user to fill]
+
+---
+
+### 3. Metric Tree
+
+Show how supporting metrics roll up to the North Star. Format as a hierarchy:
+
+```
+[North Star Metric]
+├── [Driver 1: e.g. Acquisition]
+│   ├── [L2 metric: e.g. Organic signups / week]
+│   └── [L2 metric: e.g. Paid CAC by channel]
+├── [Driver 2: e.g. Activation]
+│   ├── [L2 metric: e.g. % users completing onboarding within 7 days]
+│   └── [L2 metric: e.g. Time to first value action]
+└── [Driver 3: e.g. Retention]
+    ├── [L2 metric: e.g. Day 30 retention rate]
+    └── [L2 metric: e.g. Feature adoption depth]
+```
+
+For each L2 metric, provide:
+- **Definition:** [What exactly is measured]
+- **Why it matters:** [How it connects to the North Star]
+- **Leading or lagging?** [Leading = predictive / Lagging = outcome]
+- **How to measure:** [Data source or calculation]
+
+---
+
+### 4. Counter-Metrics
+
+[2–3 metrics to watch that prevent optimising the North Star in ways that damage the business. E.g. "If we optimise for signups, we need to watch spam account rate. If we optimise for engagement, we need to watch support ticket volume."]
+
+---
+
+### 5. Dashboard Recommendation
+
+Suggest a 3-tier dashboard structure:
+- **Exec view (weekly):** [3–5 metrics — outcomes only]
+- **Team view (daily):** [7–10 metrics — leading indicators + outputs]
+- **Diagnostic view (on demand):** [Metrics to drill into when something looks wrong]
+
+---
+
+### 6. Metric Health Check Questions
+
+[5 questions the team should ask in their weekly metrics review to turn numbers into insights. e.g. "Is our activation rate improving while retention stays flat? That suggests onboarding quality issue, not a product-market fit problem."]
+
+---
+
+## Quality Checks
+
+- [ ] North Star reflects customer value, not just business activity
+- [ ] Metric tree has 3–4 distinct drivers (not all one category)
+- [ ] Each L2 metric is classified as leading or lagging
+- [ ] Counter-metrics are included to prevent perverse incentives
+- [ ] Dashboard tiers are tailored to the product stage
+- [ ] All metric definitions are unambiguous (formula or clear description)
+
+## Example Trigger Phrases
+
+- "Build a metrics framework for [product]"
+- "What should our North Star metric be?"
+- "Create a KPI tree for [business]"
+- "Give me an AARRR breakdown for [product]"
+- "What metrics should our [team type] team track?"
@@ -0,0 +1,143 @@
+---
+name: sql-query-explainer
+description: "Explain, optimise, or translate SQL queries into plain language. Use when asked to explain a SQL query, optimise slow SQL, write a data dictionary, translate SQL to plain English for non-technical stakeholders, or review a query for correctness and performance. Works across PostgreSQL, MySQL, BigQuery, Snowflake, and standard SQL."
+---
+
+# SQL Query Explainer Skill
+
+This skill explains SQL queries in plain language, identifies optimisation opportunities, and helps communicate data logic to non-technical stakeholders. It also writes and documents new queries from natural language descriptions.
+
+## Modes
+
+Detect which mode the user needs based on their request:
+
+1. **Explain** — Translate existing SQL into plain English
+2. **Optimise** — Review SQL for performance issues and suggest improvements
+3. **Write** — Generate SQL from a natural language description
+4. **Document** — Produce a data dictionary or query documentation
+
+---
+
+## Mode 1: Explain
+
+When given a SQL query, produce:
+
+### Plain English Summary
+[1–3 sentences. What does this query do? What data does it return? Write as if explaining to a business analyst, not a developer.]
+
+### Step-by-Step Walkthrough
+
+Break the query into logical sections. For each section:
+- Quote the SQL clause
+- Explain what it does in plain English
+- Flag any complexity (e.g. window functions, subqueries, CTEs)
+
+### What the Result Looks Like
+
+[Describe the shape of the output: "Returns one row per user, with columns for X, Y, Z. Ordered by [field] descending."]
+
+### Potential Issues to Flag
+
+- [Gotchas, edge cases, or implicit assumptions in this query]
+- [e.g. "This will include NULLs in the user_id column if the LEFT JOIN finds no match"]
+
+---
+
+## Mode 2: Optimise
+
+When asked to optimise a query, produce:
+
+### Performance Assessment
+
+Rate overall: 🟢 Well-optimised / 🟡 Some improvements possible / 🔴 Significant issues
+
+### Issues Found
+
+For each issue:
+
+**Issue [N]: [Short name, e.g. "Missing index on join column"]**
+- **What it is:** [Plain explanation]
+- **Why it matters:** [Performance impact — e.g. "Full table scan on a 10M row table"]
+- **Fix:**
+```sql
+-- Before
+[original snippet]
+
+-- After
+[improved snippet]
+```
+- **Expected improvement:** [Estimate if possible]
+
+### Optimisation Checklist
+
+- [ ] SELECT * used? (Replace with specific columns)
+- [ ] Implicit type conversions on JOIN/WHERE columns?
+- [ ] Missing indexes on JOIN or WHERE columns?
+- [ ] N+1 patterns (queries inside loops)?
+- [ ] DISTINCT used where GROUP BY would be faster?
+- [ ] Window functions used where a subquery would be clearer/faster?
+- [ ] CTEs re-used or materialised unnecessarily?
+- [ ] Large IN() lists that could use a JOIN instead?
+
+---
+
+## Mode 3: Write
+
+When given a natural language description, generate the SQL query and then explain it using Mode 1.
+
+Ask the user to confirm:
+- **Database/dialect** (PostgreSQL / MySQL / BigQuery / Snowflake / SQLite / Standard SQL)
+- **Table and column names** (if known; otherwise use descriptive placeholder names like `users`, `orders`, `user_id`)
+- **Any filters, sorting, or aggregation requirements**
+
+Produce:
+1. The SQL query with inline comments
+2. Plain English explanation (Mode 1 format)
+
+---
+
+## Mode 4: Document
+
+When asked to create documentation for a query or table:
+
+### Query Documentation
+
+```
+Query: [Name]
+Purpose: [One sentence — what business question this answers]
+Author: [If provided]
+Last reviewed: [If provided]
+
+Inputs:
+  - Table: [table_name] — [what it contains]
+  - Filter: [any WHERE conditions and their business meaning]
+
+Output columns:
+  | Column | Type | Description |
+  |--------|------|-------------|
+  | [name] | [type] | [plain English description] |
+
+Assumptions:
+  - [Any implicit assumptions the query makes]
+
+Known limitations:
+  - [Edge cases not handled, data quality dependencies, etc.]
+```
+
+---
+
+## Quality Checks
+
+- [ ] Plain English explanation avoids SQL jargon
+- [ ] Optimisation suggestions include before/after SQL
+- [ ] Written queries include inline comments
+- [ ] Output shape is described (columns, row grain, ordering)
+- [ ] Dialect-specific syntax is flagged when non-standard
+
+## Example Trigger Phrases
+
+- "Explain this SQL query: [paste query]"
+- "Optimise this slow query: [paste query]"
+- "Write a SQL query that [natural language description]"
+- "Document this query for my non-technical stakeholders"
+- "Why is this query returning unexpected results?"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-delivery",
+  "version": "3.0.0",
+  "description": "Sprint & delivery skills: Sprint Planning, Technical Spec Template, A/B Test Planner, Go-to-Market Planner, Product Launch Checklist, Sprint Brief, Retro Analysis.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "sprint", "agile", "ab-testing", "go-to-market", "launch", "technical-spec"]
+}
@@ -0,0 +1,95 @@
+---
+name: ab-test-planner
+description: Designs statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, run an A/B test, calculate sample size, or interpret test results. Triggers on "A/B test", "experiment", "split test", "statistical significance", "sample size".
+---
+
+# A/B Test Planner Skill
+
+Design experiments that produce trustworthy results — not just directional signals. Every test output includes hypothesis, success metrics, sample size, duration, and a results interpretation guide.
+
+## Experiment Design Checklist
+
+Before running any test, confirm:
+- [ ] Clear hypothesis with predicted direction
+- [ ] Single primary metric (plus up to 2 guardrail metrics)
+- [ ] Minimum detectable effect (MDE) defined
+- [ ] Sample size calculated
+- [ ] Test duration estimated
+- [ ] Segment isolated (no overlap with other running tests)
+- [ ] Rollback plan defined
+
+## Hypothesis Template
+
+> "We believe that [change] will cause [primary metric] to [increase/decrease] by [X%] for [user segment], because [rationale based on data or insight]."
+
+Never run a test without a directional hypothesis. "Let's just see what happens" is not a hypothesis.
+
+## Sample Size Calculator Logic
+
+Use this formula (provide the output, not the formula, to the user):
+
+- **Baseline conversion rate:** Current rate of primary metric
+- **MDE:** Smallest change worth detecting (recommend 10–20% relative lift for most features)
+- **Statistical power:** 80% (standard)
+- **Significance level:** 95% (p < 0.05)
+
+For common scenarios, provide pre-calculated estimates:
+
+| Baseline Rate | MDE (Relative) | Required Sample per Variant |
+|---|---|---|
+| 5% | 20% | ~19,000 |
+| 10% | 15% | ~14,000 |
+| 20% | 10% | ~15,000 |
+| 40% | 10% | ~9,500 |
+| 60% | 5% | ~42,000 |
+
+Always warn: "These are estimates. Use a tool like Evan Miller's calculator or Statsig for precision."
+
+## Test Duration Guidance
+
+Minimum: 2 full weeks (to capture weekly seasonality)
+Maximum: 4 weeks (novelty effect distorts results beyond this)
+
+`Duration = Required sample ÷ (Daily traffic × % exposed)`
+
+Flag if traffic is too low to reach significance in under 8 weeks — recommend a different approach (e.g., holdout test, qualitative research).
+
+## Output Format
+
+### A/B Test Plan — [Test Name] — [Date]
+
+**Hypothesis:**
+> [Filled hypothesis template]
+
+**Variants:**
+- Control (A): [Current experience]
+- Treatment (B): [Changed experience — be specific]
+
+**Primary Metric:** [Metric name + how measured]
+**Guardrail Metrics:** [Metrics that must not degrade]
+
+**Target Segment:** [Who sees the test — % of traffic, user type]
+**Traffic Split:** [50/50 recommended unless ramp-up needed]
+
+**Sample Size Required:** ~[N] users per variant
+**Estimated Duration:** [X] weeks (based on [Y] daily eligible users)
+**Significance Threshold:** 95% confidence, 80% power
+
+**Exclusions:** [Any user segments to exclude and why]
+
+**Rollback Trigger:** If [guardrail metric] degrades by [X%], stop the test immediately.
+
+**Results Interpretation Guide:**
+- ✅ Ship if: Treatment shows [X%]+ lift on primary metric at 95% confidence AND guardrail metrics are stable
+- 🔄 Iterate if: Direction is positive but not significant — consider extending or redesigning
+- ❌ Reject if: No lift or negative direction at significance
+- ⚠️ Inconclusive: Do not ship. Do not call it a win.
+
+---
+
+## Guidelines
+
+- Always recommend against peeking at results before the test reaches planned sample size — explain p-hacking risk
+- If user wants to test multiple variants, explain the multiple comparisons problem and recommend a Bonferroni correction or a Bayesian approach
+- If traffic is very low (<1,000 users/day), recommend qualitative alternatives: moderated testing, 5-second tests, or user interviews
+- Never approve a test with no guardrail metrics — always protect revenue, retention, or core engagement
@@ -0,0 +1,114 @@
+---
+name: go-to-market-planner
+description: Builds go-to-market (GTM) plans for product launches, feature releases, and new market entries. Use when planning a product launch, writing a GTM strategy, defining launch tiers, or coordinating cross-functional launch activities. Triggers on "go-to-market", "GTM plan", "product launch plan", "launch strategy", "release plan".
+---
+
+# Go-to-Market Planner Skill
+
+Produce a complete, cross-functional GTM plan that aligns product, marketing, sales, and support around a single launch — with clear owners, timelines, and success metrics.
+
+## Launch Tier Framework
+
+Before planning, classify the launch:
+
+| Tier | Scope | Typical Effort | Examples |
+|---|---|---|---|
+| **Tier 1 — Major Launch** | New product / significant platform change | 8–12 weeks | New pricing model, platform rebrand, new product line |
+| **Tier 2 — Feature Launch** | Significant new capability | 4–6 weeks | Major feature, API release, new integration |
+| **Tier 3 — Incremental Release** | Improvement, bug fix, minor feature | 1–2 weeks | UI tweak, performance improvement, small enhancement |
+
+Always confirm tier with the user before proceeding.
+
+---
+
+## GTM Plan Output Format
+
+### GTM Plan — [Product/Feature Name] — [Launch Date]
+
+**Launch Tier:** [1 / 2 / 3]
+**Launch Owner (PM):** [Name]
+**Target Launch Date:** [Date]
+**Soft Launch Date (Beta/Limited):** [Date, if applicable]
+
+---
+
+### 1. What We're Launching
+**One-line description:** [What it is, for whom, and why now]
+**Key customer problem solved:** [Specific pain point]
+**Key differentiator:** [Why ours, why now]
+
+---
+
+### 2. Target Audience
+**Primary segment:** [Who benefits most — be specific]
+**Secondary segment:** [Who else benefits]
+**Not for:** [Who this is NOT for — helps sales and support]
+
+---
+
+### 3. Messaging
+
+**Headline:** [Customer-facing headline — lead with outcome, not feature]
+**Sub-headline:** [Supporting context — how it works or why it matters]
+**3 key messages:**
+1. [Problem solved]
+2. [How it works / what's new]
+3. [Proof / social proof / data]
+
+**Elevator pitch (30 seconds):**
+> [For [target user] who [has this problem], [product/feature] is a [category] that [key benefit]. Unlike [alternative], we [differentiator].]
+
+---
+
+### 4. Launch Activities by Function
+
+| Function | Activity | Owner | Due Date | Status |
+|---|---|---|---|---|
+| Product | Feature flagging / rollout plan | PM | [date] | |
+| Marketing | Blog post / landing page | Marketing | [date] | |
+| Marketing | Email campaign to existing users | Marketing | [date] | |
+| Marketing | Social media content | Marketing | [date] | |
+| Sales | Sales enablement deck | PM + Sales | [date] | |
+| Sales | FAQ for sales team | PM | [date] | |
+| Support | Help centre articles | Support | [date] | |
+| Support | Support team training | Support | [date] | |
+| Engineering | Monitoring/alerting in place | Eng | [date] | |
+
+---
+
+### 5. Success Metrics
+
+| Metric | Baseline | Target | Measurement Window |
+|---|---|---|---|
+| [Adoption metric] | [X] | [Y] | 30 days post-launch |
+| [Engagement metric] | [X] | [Y] | 60 days post-launch |
+| [Business metric] | [X] | [Y] | 90 days post-launch |
+
+---
+
+### 6. Risks & Contingencies
+
+| Risk | Likelihood | Impact | Mitigation |
+|---|---|---|---|
+| [Risk] | H/M/L | H/M/L | [Action if it happens] |
+
+---
+
+### 7. Launch Day Checklist
+- [ ] Feature live for [X%] of users
+- [ ] Monitoring dashboard active
+- [ ] Support team briefed
+- [ ] Blog post published
+- [ ] Email sent / scheduled
+- [ ] Sales team notified
+- [ ] Executive announcement sent (if Tier 1)
+- [ ] Rollback procedure confirmed
+
+---
+
+## Guidelines
+
+- Never plan a Tier 1 launch without at least 8 weeks of lead time
+- Always include a "Not for" section — it prevents misdirected sales and support tickets
+- Recommend a soft launch to 5–10% of users before full rollout for any Tier 1 or 2 launch
+- Post-launch retrospective should be scheduled at launch planning time — don't leave it to chance
@@ -0,0 +1,117 @@
+---
+name: product-launch-checklist
+description: Generates comprehensive pre-launch, launch day, and post-launch checklists for product releases. Use when preparing for a product launch, feature release, or major update. Triggers on "launch checklist", "pre-launch", "launch day", "release checklist", "ship checklist", "go-live checklist".
+---
+
+# Product Launch Checklist Skill
+
+Never launch without checking everything. Generate a complete, role-assigned checklist covering pre-launch readiness, launch day execution, and post-launch monitoring.
+
+## How to Use This Skill
+
+Provide:
+- Launch name and date
+- Launch tier (1 = major, 2 = feature, 3 = incremental)
+- Team members and their roles
+
+The skill generates a tiered checklist. Tier 3 launches use only the Essentials section. Tier 2 adds Marketing & Comms. Tier 1 uses all sections.
+
+---
+
+## Output Format
+
+### Launch Checklist — [Feature/Product Name] — Target Date: [Date]
+
+**Launch Tier:** [1 / 2 / 3]
+**Launch Owner:** [PM Name]
+**Engineering Lead:** [Name]
+**Go/No-Go Decision By:** [Date and time — typically 24 hours before launch]
+
+---
+
+### 🔧 PRE-LAUNCH — Engineering & Product (T-2 weeks)
+- [ ] Feature flag created and tested in staging
+- [ ] All acceptance criteria signed off by PM
+- [ ] Code reviewed and merged to main
+- [ ] QA sign-off completed (regression + new feature)
+- [ ] Performance testing completed (load, latency)
+- [ ] Security review completed (if data or auth changes)
+- [ ] Rollback procedure documented and tested
+- [ ] Monitoring and alerting configured
+- [ ] Error logging in place with correct severity levels
+- [ ] Database migrations tested on staging with production data volume
+
+### 📢 PRE-LAUNCH — Marketing & Comms (T-1 week)
+- [ ] Blog post written, reviewed, and scheduled
+- [ ] In-app announcement or tooltip configured
+- [ ] Email campaign drafted and QA'd
+- [ ] Social media posts drafted and scheduled
+- [ ] Landing page or feature page live in staging
+- [ ] Press outreach sent (Tier 1 only)
+- [ ] Product Hunt / community posts prepared (Tier 1 only)
+
+### 🎓 PRE-LAUNCH — Sales & Support (T-1 week)
+- [ ] Sales enablement one-pager completed
+- [ ] FAQ document shared with sales and support teams
+- [ ] Help centre articles written and published
+- [ ] Support team demo / training completed
+- [ ] Customer success team briefed on top accounts
+- [ ] Pricing updated (if applicable)
+- [ ] Contracts / ToS updated (if applicable)
+
+### 📊 PRE-LAUNCH — Analytics (T-1 week)
+- [ ] Analytics events firing correctly in staging
+- [ ] Dashboard configured for launch metrics
+- [ ] Baseline metrics documented
+- [ ] Success criteria documented and shared with team
+- [ ] A/B test configured (if applicable)
+
+---
+
+### ✅ GO / NO-GO DECISION — T-24 hours
+
+| Criteria | Status | Owner |
+|---|---|---|
+| All critical bugs resolved | 🟢 / 🔴 | Eng Lead |
+| QA sign-off complete | 🟢 / 🔴 | QA |
+| Rollback tested | 🟢 / 🔴 | Eng Lead |
+| Help centre articles live | 🟢 / 🔴 | Support |
+| Monitoring active | 🟢 / 🔴 | Eng Lead |
+| PM sign-off | 🟢 / 🔴 | PM |
+
+**Go / No-Go Decision:** [GO / NO-GO]
+**Decision Owner:** [PM + Eng Lead jointly]
+
+---
+
+### 🚀 LAUNCH DAY
+- [ ] Feature flag enabled for [X%] of users (start low — 5–10%)
+- [ ] Launch confirmed in team Slack/channel
+- [ ] Metrics dashboard open and being monitored
+- [ ] Error rate checked at T+15 min, T+1 hr, T+4 hr
+- [ ] Blog post published / email sent
+- [ ] Social posts live
+- [ ] Support team on standby for first 4 hours
+- [ ] PM available and reachable all day
+- [ ] Feature flag expanded to 50% if T+2hr checks pass
+- [ ] Feature flag expanded to 100% if T+4hr checks pass
+
+---
+
+### 📈 POST-LAUNCH (D+7, D+30)
+- [ ] D+7 metrics review: adoption, errors, support tickets
+- [ ] D+7 customer feedback synthesised
+- [ ] Retrospective scheduled
+- [ ] Learnings documented
+- [ ] D+30 success metrics reviewed against targets
+- [ ] Feature flag removed from codebase (clean up)
+- [ ] Follow-up features added to backlog based on feedback
+
+---
+
+## Guidelines
+
+- The Go/No-Go decision must have a named owner — "the team" is not an owner
+- Never launch on a Friday unless you have weekend engineering coverage
+- Recommend starting all launches at <10% traffic — even for simple features
+- Document rollback time: "We can revert this in X minutes" should be known before launch
@@ -0,0 +1,43 @@
+---
+name: retro-analysis
+description: Analyse sprint delivery data and produce a structured retrospective brief
+tool_integration: Jira, Miro
+---
+# Retrospective Analysis Skill
+
+## Purpose
+Generate a data-grounded retrospective brief that separates facts from feelings, so the team spends retro time on solutions rather than debating what happened.
+
+## Required Inputs
+- Sprint tickets: planned vs. completed
+- Carry-over tickets and reasons
+- Tickets reopened after closing
+- Any incidents or unplanned work
+- Sprint velocity vs. historical average
+
+## Process
+1. Calculate: completion rate, carry-over rate, unplanned work percentage
+2. Identify patterns: which ticket types were most likely to carry over? Which caused blockers?
+3. Note any process or communication breakdowns visible in the data
+4. Prepare 3 "Start / Stop / Continue" prompts based on the data — not generic, specific to this sprint
+5. Suggest 1 concrete experiment for the next sprint based on the biggest friction point
+
+## Output Format
+
+### Sprint [Number] Retrospective Brief
+
+**By the Numbers:**
+- Planned: [n] tickets | Completed: [n] | Carry-over: [n] | Completion rate: [%]
+- Unplanned work: [n] tickets ([%] of capacity)
+- Velocity: [points] vs. [average] average
+
+**What the Data Suggests:**
+[2-3 observations grounded in the numbers above]
+
+**Discussion Prompts:**
+- Start: [specific prompt]
+- Stop: [specific prompt]
+- Continue: [specific prompt]
+
+**Suggested Experiment for Next Sprint:**
+[One concrete, testable process change]
@@ -0,0 +1,43 @@
+---
+name: sprint-brief
+description: Generate a structured sprint brief from Jira sprint data and goals
+tool_integration: Jira, Slack
+---
+# Sprint Brief Skill
+
+## Purpose
+Produce a clear, scannable sprint brief that every team member — engineer, designer, PM — can read in under three minutes and understand exactly what we're doing and why.
+
+## Required Inputs
+- Sprint name and number
+- Sprint goal (1-2 sentences)
+- Ticket list with owners
+- Known dependencies or blockers
+- Carry-over items from previous sprint
+
+## Process
+1. Read sprint goal and check it's specific and measurable — flag if it's too vague
+2. Group tickets by theme or feature area
+3. Identify the critical path — which tickets must complete for the sprint goal to be met?
+4. Flag risks: tickets with unclear acceptance criteria, missing designs, unresolved dependencies
+5. Note carry-over items and whether they affect this sprint's goal
+
+## Output Format
+
+### Sprint [Number] Brief — [Dates]
+**Sprint Goal:** [1-2 sentences]
+**Why This Sprint Matters:** [Connect to quarterly OKR in 2-3 sentences]
+
+**What We're Building:**
+- [Theme 1]: [tickets and owners]
+- [Theme 2]: [tickets and owners]
+
+**Critical Path:** [The 2-3 tickets everything else depends on]
+
+**Risks to Flag:**
+- [Risk 1 + mitigation]
+- [Risk 2 + mitigation]
+
+**Carry-over from Last Sprint:** [List + impact on current goal]
+
+**Definition of Done:** [Specific, agreed criteria for sprint success]
@@ -0,0 +1,89 @@
+---
+name: sprint-planning
+description: Structures and facilitates sprint planning sessions. Use when asked to plan a sprint, organise backlog items, assign story points, create sprint goals, or prepare sprint planning meeting agendas. Triggers on phrases like "plan sprint", "sprint planning", "sprint goal", "sprint backlog".
+---
+
+# Sprint Planning Skill
+
+Transform raw backlog items into a structured, achievable sprint with clear goals, velocity-calibrated scope, and team-ready output.
+
+## What This Skill Produces
+
+- **Sprint Goal** — single, outcome-focused sentence the whole team can rally around
+- **Sprint Backlog** — prioritised list of user stories with story point estimates and acceptance criteria
+- **Capacity Plan** — team availability breakdown accounting for holidays, meetings, and focus time
+- **Sprint Planning Agenda** — structured 2-hour meeting agenda with timings
+- **Risk Flags** — blockers or dependencies that could derail the sprint
+
+## Inputs to Request From User
+
+Ask for (if not already provided):
+- Sprint duration (1 or 2 weeks)
+- Team size and velocity (average story points per sprint)
+- Top 3–5 backlog items or epics to pull from
+- Any known absences, holidays, or team events
+- Previous sprint's incomplete items (carry-overs)
+
+## Sprint Goal Formula
+
+Use this structure:
+> "This sprint we will [deliver X outcome] so that [user/business benefit], measured by [success indicator]."
+
+Never write sprint goals as task lists. Always outcome-first.
+
+## Story Point Calibration
+
+| Complexity | Points | Description |
+|---|---|---|
+| Trivial | 1 | Clearly understood, no unknowns |
+| Small | 2 | Straightforward, minor effort |
+| Medium | 3 | Some complexity, clear path |
+| Large | 5 | Complex, needs design or research |
+| Very Large | 8 | High uncertainty, may need splitting |
+| Epic | 13+ | Too large — must be split before sprint |
+
+Flag any item estimated at 8+ and recommend splitting.
+
+## Capacity Formula
+
+```
+Available capacity = (Team size × Sprint days × Focus hours/day) × Availability factor
+Focus hours/day: 6 (accounting for meetings, Slack, admin)
+Availability factor: 0.7–0.85 depending on holidays/events
+Story points to commit = Historical velocity × Availability factor
+```
+
+## Output Format
+
+### Sprint [N] — [Start Date] to [End Date]
+
+**Sprint Goal:**
+> [Goal statement]
+
+**Team Capacity:** [X] story points available (based on [Y] team members, [Z]% availability)
+
+**Sprint Backlog:**
+
+| Priority | Story | Points | Owner | Acceptance Criteria |
+|---|---|---|---|---|
+| 1 | [Story title] | [N] | [Team member] | [When X then Y] |
+
+**Carry-Overs from Previous Sprint:**
+- [Item] — Reason for carry-over: [brief explanation]
+
+**Risks & Dependencies:**
+- [Risk description] → Mitigation: [action]
+
+**Sprint Planning Agenda:**
+- 00:00–00:10 — Review sprint goal and team capacity
+- 00:10–00:40 — Walk through backlog items, confirm estimates
+- 00:40–01:20 — Assign stories, identify dependencies
+- 01:20–01:50 — Review acceptance criteria per story
+- 01:50–02:00 — Confirm sprint commitment and close
+
+## Guidelines
+
+- Always challenge stories missing acceptance criteria — flag them explicitly
+- Recommend the team commits to 80% of available capacity, not 100%
+- If no velocity data is provided, assume 20–30 points for a 5-person team as a starting point
+- Highlight any story with unclear ownership as a blocker
@@ -0,0 +1,133 @@
+---
+name: technical-spec-template
+description: Creates structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Triggers on "technical spec", "tech spec", "engineering spec", "system design doc", "API spec", "implementation spec".
+---
+
+# Technical Spec Template Skill
+
+Write technical specifications that engineers actually read — clear problem framing, unambiguous requirements, explicit decisions, and documented trade-offs.
+
+## When to Write a Tech Spec
+
+Write a tech spec when:
+- The feature requires changes to 2+ systems
+- There are significant architectural decisions to make
+- More than one engineer will work on the implementation
+- The feature has security, privacy, or compliance implications
+- Estimated effort is >5 story points
+
+Skip the spec for trivial bug fixes or 1-2 hour changes.
+
+---
+
+## Technical Spec Output Format
+
+### Technical Specification — [Feature Name]
+
+**Author:** [Name]
+**Status:** Draft | In Review | Approved | Implemented
+**Created:** [Date] | **Last Updated:** [Date]
+**Reviewers:** [Eng Lead, Architect, PM, Security if needed]
+**Related PRD:** [Link] | **Jira Epic:** [Link]
+
+---
+
+#### 1. Problem Statement
+> [2–3 sentences. What problem are we solving and why now? No solution language here.]
+
+#### 2. Goals & Non-Goals
+
+**Goals (in scope):**
+- [Specific, measurable outcome]
+- [Specific, measurable outcome]
+
+**Non-Goals (explicitly out of scope):**
+- [What this spec does NOT cover]
+- [Common assumption to shut down early]
+
+#### 3. Background & Context
+[Any prior art, related systems, or context engineers need to understand the decision space. Link to previous specs, ADRs, or research.]
+
+#### 4. Proposed Solution
+
+**High-Level Approach:**
+[2–4 sentences describing the chosen solution. Why this approach vs alternatives?]
+
+**System Architecture Diagram:**
+[Describe or embed: which services are involved, how data flows, what APIs are called]
+
+**Data Model Changes:**
+```sql
+-- New tables or schema changes
+[Include DDL or schema definition]
+```
+
+**API Design:**
+```
+[Endpoint] [Method]
+Request: { [fields and types] }
+Response: { [fields and types] }
+Error codes: [list]
+```
+
+**Key Implementation Details:**
+- [Important technical constraint or approach]
+- [Edge case handling]
+- [Third-party dependency and version]
+
+#### 5. Alternative Approaches Considered
+
+| Option | Pros | Cons | Why Rejected |
+|---|---|---|---|
+| [Alt 1] | [Benefits] | [Drawbacks] | [Reason not chosen] |
+| [Alt 2] | [Benefits] | [Drawbacks] | [Reason not chosen] |
+
+#### 6. Security & Privacy Considerations
+- Data stored: [What PII or sensitive data is involved]
+- Authentication: [How is access controlled]
+- Authorisation: [What permissions are required]
+- Encryption: [At rest / in transit requirements]
+- Compliance implications: [GDPR, SOC2, etc. if relevant]
+
+#### 7. Performance & Scalability
+- Expected load: [Requests/second, data volume]
+- Latency requirements: [P50 / P95 targets]
+- Caching strategy: [If applicable]
+- Database indexing: [New indexes required]
+- Known bottlenecks: [Where to watch]
+
+#### 8. Testing Plan
+- Unit tests: [Key scenarios to cover]
+- Integration tests: [System boundaries to test]
+- Load tests: [If performance-critical]
+- Edge cases: [Known tricky scenarios]
+- Rollback plan: [How to revert if something goes wrong]
+
+#### 9. Rollout Plan
+- Feature flag: [Yes / No — name of flag]
+- Rollout stages: [% of users at each stage]
+- Monitoring: [Metrics and alerts to set up]
+- Success criteria to progress rollout: [What needs to be true]
+- Rollback trigger: [What would cause immediate rollback]
+
+#### 10. Open Questions
+| Question | Owner | Due Date | Resolution |
+|---|---|---|---|
+| [Unresolved question] | [Name] | [Date] | [Pending] |
+
+#### 11. Implementation Timeline (Rough)
+| Phase | Work | Estimated Effort |
+|---|---|---|
+| [Phase 1] | [What gets built] | [X days/points] |
+| [Phase 2] | [What gets built] | [X days/points] |
+| Total | | [X story points] |
+
+---
+
+## Guidelines
+
+- The spec is a decision record, not a task list — document *why* decisions were made
+- All open questions must have an owner and due date
+- Security and privacy sections are never optional for features that touch user data
+- Recommend async review: engineers read first, then a 30-minute sync to resolve questions
+- Keep the spec updated as implementation progresses — stale specs are worse than no specs
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-design",
+  "version": "1.0.0",
+  "description": "Design & UX skills: UX Research Plan, Design Critique, Accessibility Audit. Create research plans with discussion guides, critique designs using JTBD and Gestalt principles, and audit for WCAG 2.2 compliance.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "design", "ux", "user-research", "accessibility", "wcag", "usability", "design-critique"]
+}
@@ -0,0 +1,175 @@
+---
+name: accessibility-audit
+description: "Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes."
+---
+
+# Accessibility Audit Skill
+
+This skill produces a structured accessibility audit based on WCAG 2.2 guidelines. It covers visual, motor, cognitive, and screen reader accessibility — with prioritised remediation for each issue found.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **What is being audited** (screen, component, full product, design spec)
+- **Description or image** of the UI
+- **Target WCAG level** (A / AA / AAA — default to AA, which is the legal standard in most jurisdictions)
+- **Known assistive technology users?** (Yes/No — if yes, which: screen reader / switch access / voice control / magnification)
+- **Platform** (Web / iOS / Android / Desktop app)
+
+## Output Structure
+
+---
+
+# Accessibility Audit: [Component or Screen Name]
+**Target standard:** WCAG 2.2 Level [AA]
+**Platform:** [Platform]
+**Date:** [Date]
+
+---
+
+## Audit Summary
+
+| Category | Issues Found | Critical | Moderate | Minor |
+|---|---|---|---|---|
+| Perceivable | | | | |
+| Operable | | | | |
+| Understandable | | | | |
+| Robust | | | | |
+| **Total** | | | | |
+
+**Overall compliance status:** ✅ Compliant / 🟡 Minor issues / 🔴 Fails AA standard
+
+---
+
+## Perceivable
+
+### 1.1 Text Alternatives
+- [ ] All images have descriptive alt text (not filename or "image")
+- [ ] Decorative images have `alt=""` to be skipped by screen readers
+- [ ] Icons without visible labels have accessible names
+- [ ] Complex images (charts, diagrams) have extended descriptions
+
+**Issues found:** [List specific issues or "None"]
+
+### 1.3 Adaptable
+- [ ] Content structure uses semantic HTML (headings, lists, landmarks) — not just visual formatting
+- [ ] Reading order in DOM matches visual order
+- [ ] Form inputs have associated labels (not placeholder text as label)
+- [ ] Data tables have proper headers and scope
+
+**Issues found:**
+
+### 1.4 Distinguishable
+- [ ] Text contrast ratio ≥ 4.5:1 (normal text) or ≥ 3:1 (large text 18px+)
+- [ ] UI component contrast ratio ≥ 3:1 against background
+- [ ] Information is not conveyed by colour alone
+- [ ] Text can be resized to 200% without loss of content
+- [ ] No content that auto-plays audio
+
+**Issues found:**
+
+---
+
+## Operable
+
+### 2.1 Keyboard Accessible
+- [ ] All interactive elements are reachable by keyboard (Tab key)
+- [ ] No keyboard traps
+- [ ] Custom components have keyboard interactions (arrow keys for menus, Escape to close modals)
+- [ ] Skip navigation link available for pages with repeated navigation
+
+**Issues found:**
+
+### 2.4 Navigable
+- [ ] Focus is visible at all times (not removed with `outline: none` without replacement)
+- [ ] Focus order is logical and predictable
+- [ ] Page/screen has a descriptive title
+- [ ] Link text is descriptive (not "click here" or "read more")
+- [ ] Headings are hierarchical (H1 → H2 → H3, no skips)
+
+**Issues found:**
+
+### 2.5 Input Modalities
+- [ ] Touch targets are at least 44x44px
+- [ ] No functionality requires complex gestures (pinch, multi-touch) without a simple alternative
+- [ ] Motion or dragging interactions have button alternatives
+
+**Issues found:**
+
+---
+
+## Understandable
+
+### 3.1 Readable
+- [ ] Language of the page is set (`lang` attribute)
+- [ ] Unusual words, abbreviations, or jargon are explained
+
+### 3.2 Predictable
+- [ ] Navigation is consistent across screens
+- [ ] Components behave consistently (same button does the same thing)
+- [ ] No unexpected context changes on focus or input
+
+### 3.3 Input Assistance
+- [ ] Error messages identify the field and describe the error in plain language (not just "Invalid input")
+- [ ] Required fields are labelled (not just with colour or asterisk alone)
+- [ ] Forms provide suggestions for correcting errors where possible
+
+**Issues found:**
+
+---
+
+## Robust
+
+### 4.1 Compatible
+- [ ] HTML is valid and well-structured
+- [ ] ARIA roles and attributes are used correctly (not to fix broken semantics)
+- [ ] Status messages (success, error, loading) are announced to screen readers without focus change
+
+**Issues found:**
+
+---
+
+## Prioritised Remediation List
+
+| Priority | Issue | WCAG Criterion | Fix | Effort |
+|---|---|---|---|---|
+| 🔴 Critical | [Issue] | [e.g. 1.4.3 Contrast] | [Specific fix] | [Low/Med/High] |
+| 🟡 Moderate | [Issue] | | | |
+| 🟢 Minor | [Issue] | | | |
+
+**Priority definitions:**
+- 🔴 Critical: Blocks access for users with disabilities. Legal risk. Fix before launch.
+- 🟡 Moderate: Significant friction. Fix in next sprint.
+- 🟢 Minor: Best practice. Address in roadmap.
+
+---
+
+## Quick Wins (Fix in < 1 hour)
+
+[List any issues that are trivially fixable — e.g. adding alt text, fixing contrast with a colour swap, adding a `lang` attribute. These are easy to ship immediately.]
+
+---
+
+## Testing Recommendations
+
+- **Manual keyboard test:** Tab through the entire flow. Can you complete every task without a mouse?
+- **Screen reader test:** VoiceOver (Mac/iOS), NVDA or JAWS (Windows). Is every piece of content and every action accessible?
+- **Colour contrast check:** Use Stark (Figma plugin) or WebAIM Contrast Checker
+- **Automated scan:** Axe DevTools or Lighthouse accessibility audit (catches ~30% of issues automatically)
+
+---
+
+## Quality Checks
+
+- [ ] Issues are mapped to specific WCAG criteria
+- [ ] Every critical issue has a specific fix recommendation
+- [ ] Quick wins are separated from larger fixes
+- [ ] Effort estimates are included for prioritisation
+- [ ] Testing recommendations are included
+
+## Example Trigger Phrases
+
+- "Audit this design for accessibility"
+- "Check WCAG compliance for [screen/component]"
+- "Give me an a11y audit of [UI description]"
+- "What accessibility issues does this design have?"
@@ -0,0 +1,130 @@
+---
+name: design-critique
+description: "Give structured, constructive feedback on any design. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Applies Jobs-to-be-Done, Gestalt principles, and usability heuristics to give actionable feedback."
+---
+
+# Design Critique Skill
+
+This skill provides structured, actionable design feedback using established UX frameworks. It balances positive observations with clear, prioritised improvement suggestions.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **What is being reviewed** (screen, flow, component, full product)
+- **Design description or attached image** (describe it if no image — the skill will still work)
+- **User goal** (what is the user trying to accomplish with this design?)
+- **Context** (web / mobile / desktop app / physical product)
+- **Stage** (early wireframe / mid-fidelity / high-fidelity / live product)
+- **Primary concern** (optional — e.g. "I'm worried the onboarding is too long" or "I think the CTA is unclear")
+
+## Output Structure
+
+---
+
+# Design Critique: [Design Name or Screen]
+
+**User goal:** [What the user needs to accomplish]
+**Context:** [Platform / Stage]
+**Critique focus:** [Primary concern if stated, otherwise "full review"]
+
+---
+
+## 1. What's Working
+
+[3–5 specific, honest observations about what the design does well. Don't manufacture praise — only include genuine strengths. Be specific: "The visual hierarchy clearly guides the eye from headline → supporting detail → CTA" is useful. "Looks clean" is not.]
+
+---
+
+## 2. Priority Issues
+
+Rank issues by impact on the user goal. Use:
+- 🔴 **High** — Blocks or significantly degrades the user's ability to complete their goal
+- 🟡 **Medium** — Causes friction or confusion but doesn't block completion
+- 🟢 **Low** — Polish or preference — nice to fix but not critical
+
+For each issue:
+
+### [Priority] Issue [N]: [Short name]
+
+**What's happening:**
+[Describe the specific design problem — be precise about which element, screen, or interaction]
+
+**Why it matters:**
+[Connect to the user goal or a specific principle — don't just say "it's confusing." Say why it creates confusion and what the consequence is for the user.]
+
+**Framework reference:**
+[Name the principle being violated — e.g. Nielsen's Heuristic #6 (Recognition over Recall), Gestalt proximity, JTBD clarity, Fitts's Law, etc.]
+
+**Recommendation:**
+[Specific, actionable suggestion. Not "make the button bigger" but "Increase the primary CTA to at least 44x44px to meet touch target guidelines; consider moving it below the form rather than inline with the input fields to reduce accidental taps."]
+
+---
+
+## 3. Heuristic Assessment
+
+Quick assessment against Nielsen's 10 Usability Heuristics — score each as ✅ Pass / 🟡 Partial / ❌ Fail:
+
+| Heuristic | Status | Note |
+|---|---|---|
+| 1. Visibility of system status | | |
+| 2. Match between system and real world | | |
+| 3. User control and freedom | | |
+| 4. Consistency and standards | | |
+| 5. Error prevention | | |
+| 6. Recognition rather than recall | | |
+| 7. Flexibility and efficiency of use | | |
+| 8. Aesthetic and minimalist design | | |
+| 9. Help users recognise, diagnose, and recover from errors | | |
+| 10. Help and documentation | | |
+
+Only include heuristics relevant to what's visible in the design — don't penalise for things not in scope.
+
+---
+
+## 4. Gestalt Principles Check
+
+[Comment on any Gestalt principles that are either well-applied or violated:]
+
+- **Proximity:** [Are related elements grouped clearly?]
+- **Similarity:** [Do similar elements look similar?]
+- **Continuity:** [Does the eye flow naturally through the design?]
+- **Figure/Ground:** [Is the primary content clearly distinguished from background?]
+- **Closure:** [Are any implied shapes or containers confusing?]
+
+---
+
+## 5. JTBD Alignment
+
+[Assess how well the design serves the stated job-to-be-done:]
+
+- **Does the design make the user's primary job obvious?** [Yes / Partially / No — explain]
+- **Are there any elements that distract from the primary job?** [List any competing CTAs, distractions, or unclear hierarchy]
+- **What emotional job does this design serve?** [Speed / Confidence / Control / Delight / Other] — and does the visual design match that emotional goal?
+
+---
+
+## 6. Top 3 Recommended Next Steps
+
+Prioritised list of the 3 most impactful changes. Each should be actionable in the next design iteration:
+
+1. [Most impactful change — specific]
+2. [Second priority]
+3. [Third priority]
+
+---
+
+## Quality Checks
+
+- [ ] "What's working" includes only genuine, specific observations
+- [ ] Every issue has a framework reference (not just subjective opinion)
+- [ ] Recommendations are specific and actionable
+- [ ] Priority levels (High/Medium/Low) reflect actual impact on user goal
+- [ ] Heuristic assessment only covers visible elements
+
+## Example Trigger Phrases
+
+- "Critique this design: [description or image]"
+- "Give me feedback on this UI/UX"
+- "Review this Figma screen for usability issues"
+- "What's wrong with this user flow?"
+- "Do a heuristic evaluation of [screen/product]"
@@ -0,0 +1,160 @@
+---
+name: ux-research-plan
+description: "Create a structured UX research plan for any product question or feature. Use when asked to write a research plan, design a user study, create a discussion guide, write screener questions, or plan usability testing. Produces a full research plan with objectives, methodology, screener, discussion guide, and synthesis framework."
+---
+
+# UX Research Plan Skill
+
+This skill creates a complete, ready-to-execute UX research plan. Output covers everything from research objectives to screener questions, discussion guide, and synthesis framework.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Research question** (what decision will this research inform?)
+- **Product area or feature** being researched
+- **Research type** (Generative / Evaluative / Usability testing / Diary study / Survey)
+- **Stage** (Discovery / Concept validation / Prototype testing / Live product)
+- **Target participants** (role, demographics, behaviour — who should we talk to?)
+- **Timeline and number of sessions**
+- **Existing assumptions or hypotheses** (optional but valuable)
+
+## Output Structure
+
+---
+
+# UX Research Plan: [Study Title]
+**Product area:** [Area]
+**Research type:** [Type]
+**Date:** [Timeline]
+**Researcher:** [Leave for user]
+
+---
+
+## 1. Research Objectives
+
+State 2–4 clear research objectives. Each objective should map to a decision that will be made differently depending on what you find.
+
+**Objective [N]:** Understand [specific thing] so we can [decision this informs].
+
+---
+
+## 2. Research Questions
+
+[5–8 questions — the actual questions you want research to answer. These are not the interview questions; they're the knowledge gaps. Organised under each objective.]
+
+**Objective 1:**
+- RQ1.1: [Research question]
+- RQ1.2: [Research question]
+
+---
+
+## 3. Methodology & Rationale
+
+**Method chosen:** [e.g. Semi-structured interviews / Usability testing / Concept testing]
+
+**Why this method:**
+[2–3 sentences. Match method to research type. If evaluative: usability testing. If generative: contextual inquiry or interviews. If testing comprehension: 5-second test or concept test.]
+
+**What this method will and won't tell us:**
+- **Will tell us:** [What this method is good at revealing]
+- **Won't tell us:** [What's out of scope — be honest about limits]
+
+**Sample size:** [Recommended number of sessions and why — e.g. "5–6 moderated interviews for generative research; 5–8 usability sessions to identify top issues"]
+
+---
+
+## 4. Participant Screener
+
+**Recruitment criteria:**
+
+| Criterion | Must Have / Nice to Have | Disqualify if |
+|---|---|---|
+| [e.g. Uses project management software daily] | Must Have | [Never uses any PM tool] |
+| [e.g. Works in a team of 5+] | Must Have | — |
+| [e.g. B2B industry] | Nice to Have | — |
+
+**Screener questions (5–8 questions):**
+
+[Q1] [Screening question — clear, not leading]
+- [Answer options — flag which qualify/disqualify]
+
+[Q2] ...
+
+**Incentive recommendation:** [Amount and format — e.g. "£50 gift voucher for a 60-min session is standard in the UK for professional participants"]
+
+---
+
+## 5. Discussion Guide
+
+Structure the session:
+
+### Opening (5 min)
+- Introduce yourself and the study
+- "We're testing the design, not you — there are no wrong answers"
+- Permission to record
+- Warm-up: [1–2 easy questions to build rapport — e.g. "Tell me about your role and what a typical week looks like"]
+
+### Core Questions (by section)
+
+**Section [A]: [Topic]** *(~X min)*
+
+1. [Open question — start broad] *[Probe: Tell me more about...]*
+2. [Follow-up to go deeper] *[Probe: Can you walk me through what happened?]*
+3. [Specific scenario or past behaviour question]
+
+**Section [B]: [Topic]** *(~X min)*
+[Continue with 2–3 questions per section]
+
+**Usability tasks (if applicable):**
+> "I'm going to ask you to try a few things with this prototype. Please think aloud as you go."
+
+- Task [N]: [Clear task instruction — write from the user's perspective, not "click on X" but "find where you would go to do Y"]
+  - **Success criteria:** [What "completing this task" looks like]
+  - **What to observe:** [Where friction typically appears]
+
+### Closing (5 min)
+- "Is there anything about [topic] we haven't covered that you think is important?"
+- "If you could change one thing about [product/concept], what would it be?"
+- Debrief and thank
+
+---
+
+## 6. Synthesis Framework
+
+After sessions, use this framework to synthesise findings:
+
+**Step 1: Session notes → Key observations**
+For each session: 3–5 specific observations (behaviours, quotes, reactions — not interpretations yet)
+
+**Step 2: Affinity mapping**
+Group observations by theme across all sessions. Aim for 4–7 clusters.
+
+**Step 3: Insight statements**
+For each cluster: "When [context], users [behaviour/experience], because [underlying need or mental model]."
+
+**Step 4: Implications**
+For each insight: "This means we should [design/product implication]" or "This challenges our assumption that [assumption]."
+
+**Step 5: Research report structure:**
+- Key findings (3–5 headlines)
+- Supporting evidence per finding
+- Design recommendations
+- Open questions for next research cycle
+
+---
+
+## Quality Checks
+
+- [ ] Research objectives map to real decisions
+- [ ] Discussion guide opens broad before going specific
+- [ ] Screener criteria are specific enough to get the right participants
+- [ ] Tasks (if usability) are written from the user's perspective
+- [ ] Synthesis framework is included
+- [ ] Incentive recommendation is included
+
+## Example Trigger Phrases
+
+- "Write a research plan for [feature or product area]"
+- "Create a discussion guide for user interviews about [topic]"
+- "Plan a usability test for [prototype or feature]"
+- "Write screener questions for [target user type]"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-discovery",
+  "version": "3.0.0",
+  "description": "Discovery & research skills: Discovery Interview Guide, Job Story Mapper, User Interview Synthesis, Assumption Mapper. Structure user research from screener to synthesis.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "user-research", "discovery", "jtbd", "interviews", "assumption-mapping"]
+}
@@ -0,0 +1,36 @@
+---
+name: assumption-mapper
+description: Extract and risk-rate all hidden assumptions in a product brief or PRD
+tool_integration: Miro
+---
+# Assumption Mapping Skill
+
+## Purpose
+Surface and prioritize the untested assumptions embedded in any product plan before development begins.
+
+## Process
+1. Read the provided brief, PRD, or concept description
+2. Extract all assumptions across four categories:
+   - **Desirability** (do users want this?)
+   - **Feasibility** (can we build it?)
+   - **Viability** (will it sustain the business?)
+   - **Usability** (can users actually use it?)
+3. For each assumption, score:
+   - Confidence (1-5): How sure are we this is true?
+   - Impact (1-5): How badly does the plan fail if this assumption is wrong?
+   - Priority = Impact minus Confidence (higher score = test this first)
+4. Output a ranked list with recommended validation methods
+
+## Output Format
+
+### Assumption Map: [Feature/Product Name]
+| Assumption | Category | Confidence | Impact | Priority Score | Recommended Validation |
+|------------|----------|------------|--------|----------------|----------------------|
+| [assumption] | [type] | [1-5] | [1-5] | [score] | [method] |
+
+#### Top 3 Assumptions to Validate First
+[Detailed recommendations for highest-priority items]
+
+## Notes
+- Flag any assumption that scores 4+ on Impact and 2 or below on Confidence as CRITICAL
+- Suggest specific research methods: usability test, survey, prototype test, data analysis
@@ -0,0 +1,90 @@
+---
+name: discovery-interview-guide
+description: Creates structured user discovery interview guides with screener questions, discussion guides, and synthesis frameworks. Use when planning user interviews, customer discovery sessions, Jobs-to-be-Done research, or problem validation. Triggers on "user interview", "discovery interview", "customer research", "JTBD", "problem validation".
+---
+
+# Discovery Interview Guide Skill
+
+Design interviews that surface genuine insight — not validation of what you already believe. Every guide follows a story-based, past-behaviour-focused structure.
+
+## Core Principles
+
+1. **Never ask about the future.** "Would you use X?" tells you nothing. "Tell me about the last time you did X" tells you everything.
+2. **Interview for behaviour, not opinion.** Opinions are cheap. Behaviour is evidence.
+3. **The 5 Whys.** Every surface answer is a door. Keep opening doors.
+4. **Confirm the problem before exploring the solution.** Never show a prototype until you've confirmed the pain exists unprompted.
+
+## Interview Structure (60 minutes standard)
+
+### 1. Warm-Up (5 min)
+Build rapport. Get them talking. Don't discuss the topic yet.
+- "Tell me a bit about your role and what a typical week looks like for you."
+- "What tools do you rely on most day-to-day?"
+
+### 2. Context Setting (10 min)
+Understand their world before diving into the problem space.
+- "Walk me through how you currently [handle the domain area]."
+- "What does that process look like from start to finish?"
+- "Who else is involved when you do this?"
+
+### 3. Problem Exploration (25 min) — THE CORE
+Surface pain without leading.
+- "Tell me about the last time you had to [relevant task]. What happened?"
+- "What was the hardest part of that?"
+- "How did you handle it?"
+- "What did you try before settling on that approach?"
+- "What does it cost you when this goes wrong?" (time, money, stress, reputation)
+- "If you could wave a magic wand and change one thing about this process, what would it be?"
+
+⚠️ **Do not mention your product or feature during this phase.**
+
+### 4. Current Solutions (10 min)
+Understand the competitive landscape from their perspective.
+- "What tools or workarounds do you use today for this?"
+- "What do you like about [current solution]? What frustrates you?"
+- "Have you tried other approaches? What happened?"
+
+### 5. Wrap-Up (10 min)
+- "Is there anything about this topic we haven't covered that you think I should know?"
+- "Is there anyone else you'd recommend I speak to?"
+- "Would you be open to a follow-up if I have more questions?"
+
+---
+
+## Output Format
+
+### Discovery Interview Guide — [Topic] — [Date]
+
+**Research Goal:** [One sentence: what decision will this research inform?]
+**Target Participant Profile:** [Role, company size, behaviour qualifier]
+
+**Screener Questions** (for recruiting):
+1. [Question] → Must answer: [Y/N or specific]
+2. [Question] → Must answer: [Y/N or specific]
+3. [Disqualifier question] → Disqualify if: [answer]
+
+**Interview Guide:**
+
+[Full structured guide using the format above, customised to the specific research topic]
+
+**Synthesis Template** (fill after each interview):
+- Key quote: "[verbatim]"
+- Core pain: [1 sentence]
+- Current workaround: [what they're doing today]
+- Intensity (1–5): [how painful is this?]
+- Surprise/unexpected finding: [anything that challenged your assumptions]
+
+**Pattern Detection** (after 5+ interviews):
+- Pain mentioned by [X/N] participants: [theme]
+- Workaround used by [X/N] participants: [theme]
+- Most emotionally charged moment in interviews: [observation]
+
+---
+
+## Guidelines
+
+- Recommend 5–8 interviews to reach thematic saturation for most discovery questions
+- Always record with permission — transcripts beat notes
+- If user is new to interviewing: remind them to stay silent after asking a question (aim for 80/20 participant-to-interviewer talking ratio)
+- Never synthesise during the interview — do it after, when you can look across sessions
+- Flag confirmation bias: if user writes questions that lead toward a predetermined answer, rewrite them as open-ended alternatives
@@ -0,0 +1,113 @@
+---
+name: job-story-mapper
+description: Writes Jobs-to-be-Done (JTBD) job stories and maps customer jobs across functional, social, and emotional dimensions. Use when defining user needs, writing job stories, conducting JTBD research, or reframing features around customer outcomes. Triggers on "job story", "JTBD", "jobs to be done", "when I want to", "user need", "hire a product".
+---
+
+# Job Story Mapper Skill
+
+Stop writing features. Start understanding jobs. This skill translates product requirements and user interviews into precise job stories that keep the team focused on outcomes — not outputs.
+
+## Jobs-to-be-Done Fundamentals
+
+A "job" is the progress a customer is trying to make in a given situation. People don't buy products — they hire them to get a job done.
+
+Three dimensions of every job:
+- **Functional job:** The practical task ("get from A to B")
+- **Emotional job:** How they want to feel ("feel confident I made the right choice")
+- **Social job:** How they want to be perceived ("look like a competent professional to my team")
+
+Great products address all three. Most roadmaps only address the functional one.
+
+---
+
+## Job Story Format
+
+**Template:**
+> When [situation/trigger], I want to [motivation/goal], so I can [expected outcome].
+
+**Not a user story:**
+User stories focus on roles and features: "As a [role] I want [feature] so that [benefit]."
+Job stories focus on situations and motivations: "When [I'm in this specific situation] I want [this capability] so I can [achieve this outcome]."
+
+**The situation is the most important part.** "When I'm in the middle of a sprint and my PM asks for an update" is a much richer trigger than "As a developer."
+
+---
+
+## Mapping Process
+
+### Step 1: Identify the main job
+One sentence: What is the core job your product is hired for?
+> "Help [user type] [accomplish outcome] when [context]."
+
+### Step 2: Break into job steps
+What are all the sub-tasks within the main job?
+(Use a job map: Define → Locate → Prepare → Confirm → Execute → Monitor → Modify → Conclude)
+
+### Step 3: Identify pain points per step
+Where does the job fall down today? Where do customers use workarounds?
+
+### Step 4: Write job stories for each pain point
+One job story per distinct situation-motivation pair.
+
+### Step 5: Map to product opportunities
+Which job stories are underserved? Which have existing solutions? Where is your differentiation?
+
+---
+
+## Output Format
+
+### Job Story Map — [Product/Feature Area] — [Date]
+
+**Core Job Statement:**
+> When [context], [user type] wants to [main job outcome], so they can [ultimate goal].
+
+---
+
+**Job Map:**
+
+| Step | Sub-Job | Current Solution | Pain Points | Underserved? |
+|---|---|---|---|---|
+| Define | [What user does] | [Tool/method used] | [Frustration] | H/M/L |
+| Locate | | | | |
+| Prepare | | | | |
+| Confirm | | | | |
+| Execute | | | | |
+| Monitor | | | | |
+| Modify | | | | |
+| Conclude | | | | |
+
+---
+
+**Job Stories (prioritised by underservice):**
+
+**Job Story 1 — [Situation label]**
+> When [specific situation], I want to [motivation], so I can [outcome].
+
+Functional dimension: [What they need to get done]
+Emotional dimension: [How they want to feel]
+Social dimension: [How they want to be perceived]
+
+Current workaround: [What they do today]
+Pain intensity: [High / Medium / Low]
+Frequency: [How often this situation occurs]
+Product opportunity: [What we could build to address this]
+
+---
+
+Repeat for each major job story.
+
+**Opportunity Scoring:**
+Rate each job story on:
+- Importance to customer (1–10)
+- Satisfaction with current solution (1–10)
+- Opportunity score = Importance + max(Importance – Satisfaction, 0)
+- Prioritise: Opportunity score > 10
+
+---
+
+## Guidelines
+
+- Never write a job story for a feature — write it for the situation that makes the feature valuable
+- If you can't identify the situation, you don't understand the job yet — go back to user research
+- Social and emotional jobs are harder to surface but often the most defensible differentiators
+- Recommend sharing job stories with engineering — they make better technical decisions when they understand the "why"
@@ -0,0 +1,38 @@
+---
+name: user-interview-synthesis
+description: Synthesise user interview transcripts into structured research findings
+tool_integration: Notion
+---
+# User Interview Synthesis Skill
+
+## Purpose
+Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights.
+
+## Process
+1. Read all provided transcripts fully before drawing conclusions
+2. Identify recurring themes (minimum 3 mentions to qualify as a theme)
+3. Categorize findings into: Pain Points, Workflow Insights, Feature Requests, Delight Moments
+4. Select 2-3 verbatim quotes per theme that best represent the pattern
+5. Draft "So What" implications for each theme — what does this mean for the product?
+
+## Output Format
+
+### Research Synthesis: [Study Name]
+**Participants:** [n]
+**Date Range:** [dates]
+**Research Questions:** [list]
+
+#### Theme 1: [Theme Name]
+- Summary (2-3 sentences)
+- Supporting quotes
+- Implication for product
+
+[Repeat for each theme]
+
+#### Recommended Next Steps
+[Specific, actionable recommendations based on findings]
+
+## Quality Checks
+- Every theme must be supported by quotes from at least 3 participants
+- Implications must connect to product decisions, not just observations
+- Avoid researcher bias — let the data lead
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-engineering",
+  "version": "1.0.0",
+  "description": "Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record. Structured outputs for engineering teams and technical PMs.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "engineering", "code-review", "incident-postmortem", "api-documentation", "adr", "architecture"]
+}
@@ -0,0 +1,146 @@
+---
+name: api-docs-writer
+description: "Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes."
+---
+
+# API Docs Writer Skill
+
+This skill transforms raw API specs, endpoint descriptions, or Postman collections into clean, developer-facing documentation following OpenAPI-adjacent conventions. Output is ready for a developer portal, README, or Notion/Confluence page.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **API or endpoint details** (raw spec, Postman export, or verbal description)
+- **Auth method** (API key / Bearer token / OAuth 2.0 / None)
+- **Base URL**
+- **Audience** (internal developers / external partners / public)
+- **Output format** (Markdown / OpenAPI YAML / Plain prose)
+
+## Output Structure
+
+For each endpoint, produce the following:
+
+---
+
+## `[METHOD] /path/to/endpoint`
+
+**Summary:** [One line — what this endpoint does]
+
+**Description:** [2–4 sentences. When to use this endpoint. What it returns. Any important behaviour to know (pagination, rate limits, async processing, etc.)]
+
+**Authentication:** [Required / Optional — method]
+
+---
+
+### Request
+
+**Headers:**
+
+| Header | Required | Description |
+|---|---|---|
+| `Authorization` | Yes | `Bearer <token>` |
+| `Content-Type` | Yes | `application/json` |
+
+**Path Parameters:**
+
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `id` | string | Yes | Unique identifier for the resource |
+
+**Query Parameters:**
+
+| Parameter | Type | Required | Default | Description |
+|---|---|---|---|---|
+| `limit` | integer | No | 20 | Max results per page (1–100) |
+| `cursor` | string | No | — | Pagination cursor from previous response |
+
+**Request Body:**
+
+```json
+{
+  "field_name": "value",
+  "another_field": 42
+}
+```
+
+| Field | Type | Required | Description |
+|---|---|---|---|
+| `field_name` | string | Yes | [Plain description of what this field does] |
+| `another_field` | integer | No | [Description. Include valid range or enum values if applicable] |
+
+---
+
+### Response
+
+**Success Response: `200 OK`**
+
+```json
+{
+  "id": "abc123",
+  "status": "active",
+  "created_at": "2025-04-01T10:00:00Z"
+}
+```
+
+| Field | Type | Description |
+|---|---|---|
+| `id` | string | Unique identifier for the created/retrieved resource |
+| `status` | string | Current status. Enum: `active`, `inactive`, `pending` |
+| `created_at` | ISO 8601 string | Timestamp of creation in UTC |
+
+---
+
+### Error Codes
+
+| Status Code | Error Code | Description | How to Resolve |
+|---|---|---|---|
+| `400` | `INVALID_REQUEST` | Request body is malformed or missing required fields | Check request body against schema above |
+| `401` | `UNAUTHORIZED` | Missing or invalid authentication token | Verify your API key or refresh your token |
+| `404` | `NOT_FOUND` | The requested resource does not exist | Check the ID in the path parameter |
+| `429` | `RATE_LIMITED` | Too many requests | Back off and retry after `Retry-After` header value |
+| `500` | `INTERNAL_ERROR` | Unexpected server error | Retry with exponential backoff; contact support if persists |
+
+---
+
+### Code Examples
+
+Produce examples in at least 2 languages relevant to the audience (default: cURL + Python):
+
+**cURL:**
+```bash
+curl -X POST https://api.example.com/v1/endpoint \
+  -H "Authorization: Bearer YOUR_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"field_name": "value"}'
+```
+
+**Python:**
+```python
+import requests
+
+response = requests.post(
+    "https://api.example.com/v1/endpoint",
+    headers={"Authorization": "Bearer YOUR_TOKEN"},
+    json={"field_name": "value"}
+)
+data = response.json()
+```
+
+---
+
+## Quality Checks
+
+- [ ] Every parameter is documented (type, required/optional, description)
+- [ ] Response fields are fully documented with types
+- [ ] All relevant error codes are listed with resolution guidance
+- [ ] Code examples are copy-paste runnable (no pseudocode)
+- [ ] Auth method is clearly stated at the top
+- [ ] Enum values are listed where applicable
+- [ ] Pagination documented if the endpoint is a list endpoint
+
+## Example Trigger Phrases
+
+- "Document this API endpoint: [paste spec or description]"
+- "Turn this Postman collection into developer docs"
+- "Write API reference docs for [endpoint]"
+- "Write a developer guide for our [product] API"
@@ -0,0 +1,117 @@
+---
+name: architecture-decision-record
+description: "Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs."
+---
+
+# Architecture Decision Record (ADR) Skill
+
+This skill produces a complete Architecture Decision Record (ADR) following the Nygard format — the most widely adopted standard. ADRs document the reasoning behind significant technical decisions so future team members understand not just *what* was decided, but *why*.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Decision title** (brief, e.g. "Use PostgreSQL as primary datastore")
+- **Context** (what situation led to this decision needing to be made?)
+- **Options considered** (at least 2; if only 1 is given, prompt for alternatives that were considered or ruled out)
+- **Decision made** (which option was chosen)
+- **Reason for choice**
+- **Status** (Proposed / Accepted / Deprecated / Superseded)
+- **Author and date**
+
+## Output Structure
+
+---
+
+# ADR-[NNN]: [Decision Title]
+
+**Date:** [YYYY-MM-DD]
+**Status:** [Proposed / Accepted / Deprecated / Superseded by ADR-NNN]
+**Author(s):** [Name(s)]
+**Deciders:** [Who had final say — individual or team]
+
+---
+
+## Context
+
+[3–6 sentences. Describe the situation, constraints, and forces at play that made this decision necessary. Include: the problem being solved, relevant system state, team constraints, timeline pressures, or non-negotiable requirements. Write as if explaining to someone joining the team 18 months from now who has no prior context.]
+
+**Key constraints:**
+- [Constraint 1: e.g. "Must be deployable on-premise for enterprise customers"]
+- [Constraint 2: e.g. "Team has no prior Go experience"]
+- [Add as many as are relevant]
+
+---
+
+## Options Considered
+
+For each option, produce:
+
+### Option [N]: [Name]
+
+**Description:** [What this option is — 1–3 sentences]
+
+**Pros:**
+- [Pro 1]
+- [Pro 2]
+
+**Cons:**
+- [Con 1]
+- [Con 2]
+
+**Why this was ruled out (if not chosen):** [Honest reason]
+
+---
+
+## Decision
+
+**We will [chosen option].**
+
+[2–4 sentences explaining the decision in plain language. This should be readable in isolation — someone should understand the decision from this paragraph alone without reading the full document.]
+
+---
+
+## Consequences
+
+### Positive Consequences
+- [What this decision enables or improves]
+- [What risk it mitigates]
+
+### Negative Consequences / Accepted Tradeoffs
+- [What we're giving up or taking on as a result of this decision]
+- [Technical debt or limitations introduced]
+- [What must now be true for this decision to remain valid]
+
+### Risks
+- [What could cause this decision to be wrong in hindsight]
+- [What would trigger us to revisit this decision]
+
+---
+
+## Implementation Notes
+
+[Optional but valuable: any specific patterns, gotchas, or guidance for the team implementing based on this decision. Link to relevant tickets, RFCs, or design docs if applicable.]
+
+---
+
+## Review Date
+
+[Optional: "This decision should be reviewed if [condition] — e.g. team grows beyond 20 engineers, or traffic exceeds 10M requests/day."]
+
+---
+
+## Quality Checks
+
+- [ ] Context explains the *why* — not just the *what*
+- [ ] At least 2 options are documented (including the rejected ones)
+- [ ] Rejected options include honest reasons for rejection
+- [ ] Consequences include *negative* consequences — no decision is consequence-free
+- [ ] Decision is stated in plain language in the Decision section
+- [ ] Risks section identifies what would invalidate this decision
+- [ ] Written for someone with no prior context on this decision
+
+## Example Trigger Phrases
+
+- "Write an ADR for using [technology]"
+- "Document our decision to [architectural choice]"
+- "Create an architecture decision record for [topic]"
+- "Help me write up why we chose [option] over [alternative]"
@@ -0,0 +1,114 @@
+---
+name: code-review-checklist
+description: "Generate a tailored code review checklist for any PR, language, or risk level. Use when asked to create a code review checklist, review guidelines, PR standards, or quality gates for a codebase. Produces a structured, prioritised checklist adapted to the specific language, PR type, and risk level."
+---
+
+# Code Review Checklist Skill
+
+This skill generates a structured, prioritised code review checklist tailored to a specific PR, language, and risk level. It helps reviewers be thorough without being bureaucratic.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Programming language(s)** (e.g. Python, TypeScript, Go, Java)
+- **PR type** (new feature / bug fix / refactor / performance improvement / security patch / infrastructure change)
+- **Risk level** (Low: internal tooling, Low traffic / Medium: user-facing feature / High: payment, auth, data pipeline, public API)
+- **Team context** (optional: team size, seniority mix, any known recurring issues)
+
+## Output Structure
+
+### 1. Checklist Header
+
+**PR:** [Title if provided]
+**Language:** [Language]
+**Type:** [PR Type]
+**Risk Level:** [Low / Medium / High]
+**Estimated review depth:** [Quick scan ~15 min / Standard ~30 min / Deep review ~60 min+]
+
+---
+
+### 2. The Checklist
+
+Organise into sections. Mark each item with a priority indicator:
+- 🔴 **MUST** — Blocking. PR should not merge without this.
+- 🟡 **SHOULD** — Important. Address before merge unless there's a good reason not to.
+- 🟢 **CONSIDER** — Nice to have. Worth a comment but not blocking.
+
+#### Section A: Correctness
+- 🔴 Does the code do what the ticket/requirement describes?
+- 🔴 Are edge cases handled? (nulls, empty arrays, zero values, max values)
+- 🔴 Are error states handled and surfaced appropriately?
+- 🟡 Does the happy path have adequate test coverage?
+- 🟡 Are failure paths tested?
+
+#### Section B: Security (scale with risk level — expand for High risk PRs)
+- 🔴 [High risk only] Is user input sanitised before use in queries or commands?
+- 🔴 [High risk only] Are auth/permission checks in place?
+- 🟡 Are secrets/credentials committed anywhere? (check .env handling)
+- 🟡 Are third-party dependencies known-safe versions?
+
+#### Section C: Performance
+- 🟡 Are there N+1 query patterns in database calls?
+- 🟡 Is there unnecessary work inside loops?
+- 🟢 Are database queries indexed appropriately?
+- 🟢 Is caching considered where appropriate?
+
+#### Section D: Readability & Maintainability
+- 🟡 Are function and variable names clear without needing a comment to explain them?
+- 🟡 Are complex logic blocks explained with inline comments?
+- 🟢 Is the code consistent with existing patterns in the codebase?
+- 🟢 Are there any magic numbers that should be named constants?
+
+#### Section E: Language-Specific Checks
+[Populate this section based on the specified language. Examples below:]
+
+**Python:**
+- 🟡 Are type hints used on function signatures?
+- 🟡 Are exceptions caught specifically (not bare `except:`)?
+- 🟢 Does it follow PEP 8 (or the team's linter config)?
+
+**TypeScript/JavaScript:**
+- 🔴 Are there any `any` types that should be properly typed?
+- 🟡 Are async/await patterns used consistently (no mixed Promise.then chains)?
+- 🟢 Are there unnecessary re-renders in React components?
+
+**Go:**
+- 🔴 Are errors checked (not ignored with `_`)?
+- 🟡 Are goroutines properly managed to prevent leaks?
+- 🟢 Are exported functions documented?
+
+#### Section F: PR Hygiene
+- 🟡 Is the PR a reasonable size? (>500 lines diff suggests it should be split)
+- 🟡 Does the PR description explain *why*, not just *what*?
+- 🟢 Are there linked tickets or context in the PR description?
+- 🟢 Are migration scripts or deployment notes included if needed?
+
+---
+
+### 3. Risk-Specific Additions
+
+For **High risk** PRs, always add:
+- 🔴 Has this been tested in a staging environment?
+- 🔴 Is there a rollback plan?
+- 🔴 Has a second reviewer been assigned?
+
+For **Infrastructure / DB changes**, always add:
+- 🔴 Are migrations backward-compatible?
+- 🔴 Has the migration been tested against production data volume?
+
+---
+
+## Quality Checks
+
+- [ ] Checklist is tailored to the specified language (not generic)
+- [ ] Risk level is reflected in the MUST vs SHOULD balance
+- [ ] Language-specific section covers the most common issues for that language
+- [ ] PR hygiene section is always present
+- [ ] High-risk additions are included when risk level = High
+
+## Example Trigger Phrases
+
+- "Generate a code review checklist for a Python bug fix PR"
+- "Give me a review checklist for a high-risk TypeScript auth change"
+- "What should I check in this Go PR?"
+- "Create PR review standards for our team"
@@ -0,0 +1,144 @@
+---
+name: incident-postmortem
+description: "Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Generates a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items."
+---
+
+# Incident Postmortem Skill
+
+This skill produces a complete, blameless incident postmortem document following industry-standard format. Output is ready to share with engineering teams, leadership, and affected stakeholders.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Incident title / ID**
+- **Severity** (P1 / P2 / P3 or SEV1 / SEV2 / SEV3)
+- **Date and duration** of the incident
+- **What happened** (rough notes are fine — the skill will structure them)
+- **Services or systems affected**
+- **Customer impact** (how many users, what was degraded)
+- **How it was detected**
+- **How it was resolved**
+- **Initial thoughts on root cause**
+- **Action items already identified** (optional)
+
+## Output Structure
+
+---
+
+# Incident Postmortem: [Incident Title]
+
+**Incident ID:** [ID]
+**Severity:** [P1/P2/P3]
+**Date:** [Date]
+**Duration:** [Start time → Resolution time — total duration]
+**Status:** [Resolved / Monitoring / Ongoing]
+**Author:** [Leave blank for user to fill]
+**Last updated:** [Date]
+
+---
+
+## Executive Summary
+
+[3–5 sentences. Describe what happened, who was affected, and what was done to resolve it. Written for a non-technical stakeholder. No jargon. No blame.]
+
+---
+
+## Impact
+
+| Dimension | Details |
+|---|---|
+| **Users affected** | [Number or percentage] |
+| **Services degraded** | [List affected services] |
+| **Business impact** | [Revenue, SLA breach, support tickets, etc. if known] |
+| **Duration** | [Total time from first detection to full resolution] |
+
+---
+
+## Timeline
+
+List events in chronological order. Each entry: `[HH:MM UTC] — [What happened. Who did what. What changed.]`
+
+Rules for timeline entries:
+- Use passive or system-focused language — avoid "X made a mistake"
+- Include: first symptom, detection, escalation, hypothesis tested, fix applied, confirmation of resolution
+- Note time between key events (e.g. "22 minutes between detection and escalation")
+
+---
+
+## Root Cause
+
+**Primary root cause:** [One clear sentence. Technical but plain. "A misconfigured deployment config caused..."]
+
+**Contributing factors:**
+- [Factor 1 — e.g. lack of canary deployment meant change hit 100% of traffic immediately]
+- [Factor 2 — e.g. alert threshold was set too high to catch the initial degradation]
+- [Factor 3 — add as many as are relevant]
+
+**Why did our existing safeguards not prevent this?**
+[Honest paragraph explaining why monitoring, tests, or processes didn't catch this earlier. This is where blameless analysis matters most — focus on system gaps, not individual failures.]
+
+---
+
+## Detection
+
+- **How was it first detected?** [Customer report / automated alert / internal monitoring / manual observation]
+- **Time from incident start to detection:** [X minutes]
+- **Should we have detected this faster?** [Yes / No — and why]
+
+---
+
+## Resolution
+
+**What fixed it?** [Clear description of the actual fix — one paragraph]
+**Why did this work?** [Brief technical explanation]
+**Was there a temporary mitigation before full resolution?** [Yes/No — describe if yes]
+
+---
+
+## Action Items
+
+| # | Action | Owner | Due Date | Priority |
+|---|---|---|---|---|
+| 1 | [Specific, testable action] | [Team or person] | [Date] | P1/P2/P3 |
+
+Rules for action items:
+- Each action must be specific enough to close as "done" or "not done" — no vague items like "improve monitoring"
+- Distinguish between: **Prevent recurrence** (fix the root cause), **Improve detection** (catch it faster next time), **Improve response** (resolve it faster next time)
+- Assign a real owner — not "team" or "TBD" if avoidable
+- Flag P1 actions as items that block the incident from being marked fully closed
+
+---
+
+## What Went Well
+
+[3–5 honest observations about the response. Include: fast collaboration, good runbooks used, effective escalation, clear communication. This section builds team confidence and reinforces good habits.]
+
+---
+
+## Lessons Learned
+
+[3–5 key insights from this incident that are worth sharing beyond this team. Write these as transferable lessons — e.g. "Our runbook for database failover didn't account for read-replica lag. All runbooks involving database failover should be reviewed."]
+
+---
+
+## Communication Log
+
+[Optional — list external communications sent: status page updates, customer emails, support responses. Include timestamps.]
+
+---
+
+## Quality Checks
+
+- [ ] Timeline has no blame-focused language
+- [ ] Root cause is specific (not "human error")
+- [ ] Contributing factors explain the systemic gaps
+- [ ] Every action item has an owner and due date
+- [ ] "What went well" section is genuine, not token
+- [ ] Executive summary is readable by non-technical leadership
+
+## Example Trigger Phrases
+
+- "Write a postmortem for the [incident name] outage"
+- "Help me write a P1 incident report"
+- "Generate an RCA document for [service] going down on [date]"
+- "Draft a blameless postmortem from these notes: [paste notes]"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-essentials",
+  "version": "3.0.0",
+  "description": "Core PM skills: PRD Template, Meeting Notes, Stakeholder Update, User Research Synthesis, and Competitive Analysis. The 5 skills every PM needs first.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "prd", "meeting-notes", "stakeholder", "user-research", "competitive-analysis"]
+}
@@ -0,0 +1,251 @@
+---
+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
+```
+
+## 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
@@ -0,0 +1,260 @@
+---
+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
+- Decisions or conclusions reached
+
+### 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 general discussion
+- 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 (@mention them)
+- 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
+
+Template additions:
+- **Recent Wins**: What's going well
+- **Challenges**: What's not going well
+- **Career Discussion**: Development topics
+- **Feedback**: For both parties
+
+### Sprint Planning
+Focus on:
+- Story acceptance criteria
+- Sizing/estimation decisions
+- Dependency identification
+- Sprint commitment
+
+Template additions:
+- **Sprint Goal**: What we're committing to
+- **Story Points**: Capacity and estimates
+- **Dependencies**: External blockers
+- **Definition of Done**: Acceptance criteria
+
+### Product Reviews
+Focus on:
+- Design decisions
+- User feedback discussed
+- Changes requested
+- Launch readiness assessment
+
+Template additions:
+- **Design Decisions**: What was approved/rejected
+- **User Feedback**: Key insights discussed
+- **Open Design Questions**: What needs iteration
+- **Launch Criteria**: Remaining requirements
+
+### Stakeholder Sync
+Focus on:
+- Status updates delivered
+- Concerns raised
+- Approvals given
+- Escalation needs
+
+Template additions:
+- **Status Overview**: High-level progress
+- **Approvals Obtained**: Sign-offs received
+- **Escalations**: Issues raised to stakeholders
+- **Next Sync**: When and what to cover
+
+## 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
+
+**Decision**: Run mobile beta with 100 users before full launch
+**Context**: Need to validate improvements on diverse devices
+**Owner**: Jennifer (Design) to coordinate with QA
+**Deadline**: February 10
+
+## Action Items
+- [ ] **Update Q1 roadmap deck with new prioritization** - @Tom - Due: Jan 22
+- [ ] **Schedule alignment meeting with support team about dashboard delay** - @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
+- [ ] **Identify 100 beta users for mobile** - @Tom - Due: Feb 1
+
+## 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
+- Sales has 3 enterprise deals waiting on dashboard feature
+
+**Resource Constraints**
+- Currently 4 engineers available (down from 6 last quarter due to attrition)
+- Design team can support both initiatives but at reduced capacity
+- QA team needs 2 weeks for thorough testing on mobile
+- One engineer on loan to security team through February
+
+**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
+- Need to communicate clearly with Sales about timeline change
+
+**Mobile Implementation Plan**
+- Week 1-2: Design refinements based on user feedback
+- Week 3-4: Engineering implementation
+- Week 5: Internal testing
+- Week 6: Beta with 100 users
+- Week 7: Full rollout
+
+## Open Questions
+- **Question**: What's the impact on enterprise pipeline if we delay dashboard?  
+  **Owner**: Sarah will check with Sales leadership  
+  **By When**: January 23
+
+- **Question**: Can we do a limited beta of dashboard for enterprise customers?  
+  **Owner**: Tom will explore MVP scope with Mike  
+  **By When**: January 25
+
+- **Question**: What's our plan if mobile improvements don't hit target metrics?
+  **Owner**: Tom will create contingency plan
+  **By When**: January 27
+
+## Next Steps
+1. Tom to send updated roadmap to leadership by EOD Wednesday (Jan 22)
+2. Team to begin sprint planning for mobile improvements next Monday (Jan 27)
+3. Follow-up meeting on Feb 1 to review progress and validate prioritization
+4. Sarah to present decision rationale to executive team on Jan 24
+
+---
+
+**Next Meeting**: February 1, 2026 - Progress Check-in
+**Notes Sent**: January 20, 2026 5:30 PM
+```
+
+## Notes Distribution
+
+**Subject Line Format**: "[Meeting Type] Notes - [Date] - [Key Topic]"
+
+Example: "Product Roadmap Review Notes - Jan 20 - Q1 Prioritization"
+
+**Recipients**:
+- All attendees
+- Anyone mentioned in action items
+- Anyone who requested notes
+
+**Follow-Up**:
+- Send reminder 3 days before action item due dates
+- Weekly summary of all open action items
+- Mark action items as complete and share updates
@@ -0,0 +1,144 @@
+---
+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%
+
+## Context & Background
+
+**Why Now**: Customer satisfaction has declined 15% over the past 6 months, primarily due to slow response times. Our top competitor launched a unified support dashboard last quarter, and we're hearing about it in sales calls. Support team turnover is at 45% annually, with "tool complexity" cited as a top frustration.
+
+**Strategic Alignment**: This aligns with our Q1 company objective to "Improve customer retention by 10%" and our support team's OKR to "Reduce average handle time by 25%."
+
+**User Research Summary**: We conducted interviews with 12 support agents and observed 20 hours of support sessions. Key findings:
+- Agents spend 35% of their time finding context from previous interactions
+- 65% of escalations are due to lack of conversation history
+- Agents rated tool-switching as their #1 daily frustration (9.2/10 pain)
+- Current NPS for support experience is -12
+
+## User Stories & Use Cases
+
+**US1: Unified Inbox**
+As a support agent, I want to see all customer inquiries in one place so that I don't miss urgent requests and can prioritize effectively.
+
+Acceptance Criteria:
+- Inbox shows inquiries from email, chat, and social media
+- Inquiries are sorted by priority (urgent, high, normal, low)
+- Agent can filter by channel, customer, or status
+- Real-time updates when new inquiries arrive
+
+**US2: Cross-Channel Context**
+As a support agent, I want to see the full conversation history regardless of channel so that I can provide consistent, informed responses without asking customers to repeat themselves.
+
+Acceptance Criteria:
+- Timeline view shows all interactions chronologically
+- Each interaction displays channel, timestamp, and content
+- Customer profile shows demographics and account information
+- Previous issues and resolutions are accessible
+
+[Continue with 5-7 total user stories...]
+```
@@ -0,0 +1,219 @@
+---
+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
+- Engineering allocated resources to billing integration fix
+
+## Key Metrics
+| Metric | Current | Target | Trend | Status |
+|--------|---------|--------|-------|--------|
+| Onboarding Completion | 45% | 60% | → | 🟡 |
+| Time to First Value | 4.2 min | 3.0 min | ↓ | 🟢 |
+| Setup Support Tickets | 45/week | <30/week | ↓ | 🟢 |
+| User Activation Rate | 52% | 65% | → | 🟡 |
+
+## Risks & Blockers
+
+**HIGH: Billing System Integration Delay**
+- **Impact**: Prevents users from completing onboarding flow; delays launch by 1-2 weeks
+- **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? (See below)
+
+**MEDIUM: Mobile Testing Coverage**
+- **Impact**: Some edge cases on older Android devices not tested
+- **Mitigation**: Partnering with QA to expand test matrix; running beta with internal users on diverse devices
+
+## Upcoming Milestones
+
+**Next 30 Days:**
+- Resolve billing integration (Feb 3)
+- Launch onboarding redesign (Feb 5 or Feb 12 depending on decision)
+- Begin measuring impact on conversion (Feb 12)
+
+**Next 90 Days:**
+- Iterate based on production data (March)
+- Extend to mobile app (April)
+- Launch advanced features (May)
+
+## 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
+- Timeline: Launch Feb 5
+
+**Option B: Wait for Billing Fix**
+- Pros: Fully integrated experience from day one, no technical debt
+- Cons: Delays benefits by 2 weeks, Q1 metric targets at risk, team momentum lost
+- Timeline: Launch Feb 12
+
+**Recommendation**: Option A. The onboarding improvements are valuable independently, and the old payment flow works fine. Waiting risks missing Q1 targets and delays validated improvements from reaching users.
+
+**Timeline**: Need decision by Jan 22 for Feb 5 launch.
+
+---
+
+**Questions?** Reply to this email or ping me on Slack.
+```
+
+## Frequency Guidance
+
+**Daily standups**: 
+- Ultra-brief (3 bullets)
+- What shipped yesterday
+- What's shipping today
+- Blockers
+
+**Weekly updates**:
+- Use full template above
+- Focus on progress and risks
+- Keep to 1 page
+
+**Monthly reviews**:
+- Deeper metrics analysis
+- Strategic reflections
+- Quarterly goal progress
+- Longer format (2-3 pages) acceptable
+
+**Quarterly business reviews**:
+- Comprehensive analysis
+- Trends over time
+- Strategic recommendations
+- Presentation format
+
+## Adaptation by Audience
+
+### For C-Suite
+- Lead with business impact
+- Connect to company OKRs
+- Focus on strategy and outcomes
+- Minimize technical details
+
+### For Product/Engineering Leadership
+- Include technical context
+- Show sprint/milestone progress
+- Discuss architecture implications
+- Reference technical debt
+
+### For Cross-Functional Teams
+- Balance technical and business context
+- Highlight dependencies
+- Call out collaboration needs
+- Make asks explicit
+
+### For Board/Investors
+- Focus on metrics and traction
+- Competitive positioning
+- Market opportunities
+- Financial implications
@@ -0,0 +1,229 @@
+---
+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.
+
+**Recommended Action**: 
+- Design a "Quick Start" path that gets users to first value in <3 minutes
+- Move advanced configuration to contextual help within the app
+- Test with 5-10 new users before full rollout
+- Expected impact: +20-30% activation rate improvement
+```
+
+## Template Output Structure
+
+When synthesizing research, use this structure:
+
+```markdown
+# User Research Synthesis: [Research Topic]
+
+## Research Overview
+- **Date**: [Date range]
+- **Methodology**: [Interview/Survey/Testing]
+- **Participants**: [Number] [User types]
+- **Research Questions**: 
+  1. [Question 1]
+  2. [Question 2]
+  3. [Question 3]
+
+## Executive Summary
+[2-3 sentence overview of key findings and implications]
+
+## Key Themes
+
+### Theme 1: [Theme Name]
+[Full theme documentation as shown in example above]
+
+### Theme 2: [Theme Name]
+[Full theme documentation]
+
+[Continue with 4-8 themes]
+
+## Pain Points Summary
+
+| Pain Point | Severity | Frequency | Current Workaround |
+|------------|----------|-----------|-------------------|
+| [Pain 1] | High | 10/12 users | [How they cope] |
+| [Pain 2] | Medium | 7/12 users | [How they cope] |
+
+## Feature Requests
+
+### Must-Have
+1. **[Request]** - Mentioned by [X] participants
+   - Quote: "[Representative quote]"
+   - Underlying need: [Why they want this]
+
+### High Value
+[Similar structure]
+
+### Nice-to-Have
+[Similar structure]
+
+## Recommendations
+
+### High Priority (0-3 months)
+1. **[Recommendation]**
+   - Supporting evidence: [Data from research]
+   - Expected impact: [What will improve]
+   - Effort estimate: [Rough sizing]
+
+### Medium Priority (3-6 months)
+[Similar structure]
+
+### Future Consideration (6+ months)
+[Similar structure]
+
+## Open Questions
+1. [Question requiring more research]
+2. [Uncertainty to validate]
+3. [Follow-up study needed]
+
+## Appendix
+- Interview guide used
+- Full participant demographics
+- Raw notes/transcripts (link)
+```
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-gtm",
+  "version": "1.0.0",
+  "description": "Marketing & GTM skills: Go-To-Market Planner, Content Calendar, Competitor Teardown, Email Campaign. Build positioning statements, messaging pillars, feature lists, use cases, and launch campaigns.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "marketing", "gtm", "positioning", "content-calendar", "competitor-analysis", "email-campaign"]
+}
@@ -0,0 +1,78 @@
+---
+name: competitor-teardown
+description: "Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations."
+---
+
+# Competitor Teardown Skill
+
+This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Your product** (name + one-line description)
+- **Competitors to analyse** (list 2–5 names; if not provided, ask)
+- **Analysis depth** (quick overview / detailed teardown)
+- **Primary use case for this analysis** (e.g. sales enablement, investor deck, internal strategy, product planning)
+
+## Output Structure
+
+### 1. Competitive Landscape Overview
+
+One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary.
+
+### 2. Positioning Map
+
+Describe a 2x2 positioning map in text form (since you can't render images):
+
+- Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness")
+- Place each competitor in one quadrant with a one-sentence rationale
+- Place the user's product and highlight the strategic implication
+
+### 3. Feature Comparison Table
+
+| Feature / Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
+|---|---|---|---|---|
+| [Feature] | ✅ / ❌ / 🟡 Partial | | | |
+
+Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk.
+
+Include 10–15 rows. If user hasn't provided feature details, note which cells need to be verified.
+
+### 4. Messaging Analysis
+
+For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):
+
+**[Competitor Name]**
+- **Their primary claim:** [what they say they do]
+- **Target audience signal:** [who they seem to be targeting based on language/imagery]
+- **Emotional hook:** [fear / aspiration / authority / speed / simplicity]
+- **Gap or weakness in their messaging:** [what they don't address that your product could own]
+
+### 5. SWOT Summary
+
+Produce a clean SWOT for the user's product in the context of this competitive landscape:
+
+- **Strengths:** [2–3 genuine differentiators]
+- **Weaknesses:** [2–3 honest gaps or vulnerabilities]
+- **Opportunities:** [2–3 market gaps or competitor weaknesses to exploit]
+- **Threats:** [2–3 competitor moves or market shifts to watch]
+
+### 6. Strategic Recommendations
+
+3–5 actionable recommendations based on the analysis. Frame each as: **"Given [observation], [your product] should [action] to [outcome]."**
+
+## Quality Checks
+
+- [ ] Axes on positioning map are meaningful and specific to this market
+- [ ] Feature table includes strategic notes on key differentiators
+- [ ] Messaging analysis covers all named competitors
+- [ ] SWOT is honest — Weaknesses and Threats should not be softened
+- [ ] Recommendations are specific and actionable, not generic strategy advice
+
+## Example Trigger Phrases
+
+- "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
+- "Tear down [Competitor]'s positioning"
+- "Give me a competitive landscape for [market]"
+- "Build a SWOT for our product against [competitor]"
@@ -0,0 +1,58 @@
+---
+name: content-calendar
+description: "Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks."
+---
+
+# Content Calendar Skill
+
+This skill generates a structured content calendar from brand inputs. It produces ready-to-use calendar entries with topics, formats, channels, and opening hooks — usable for social media, blogs, newsletters, or multi-channel campaigns.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Brand or product name**
+- **Target audience** (who are you trying to reach?)
+- **Primary content goal** (awareness / lead gen / retention / thought leadership)
+- **Channels** (e.g. LinkedIn, Instagram, newsletter, blog, X/Twitter)
+- **Cadence** (daily / 3x per week / weekly / monthly)
+- **Timeframe** (e.g. 4 weeks, Q2)
+- **Brand pillars or themes** (optional — if not provided, derive 3 from the product description)
+
+## Output Structure
+
+### 1. Content Pillars (if not provided)
+
+Derive 3–4 content pillars from the brand/product description. Each pillar = a recurring theme that anchors multiple posts. Label each one clearly (e.g. "Pillar 1: Industry Education", "Pillar 2: Product Stories").
+
+### 2. Calendar Table
+
+Produce a weekly table for each week requested. Format:
+
+| Date | Pillar | Topic | Format | Channel | Opening Hook |
+|---|---|---|---|---|---|
+| Mon 7 Apr | Education | [Topic title] | Carousel / Article / Short video / Thread | LinkedIn | [First sentence or headline of the post] |
+
+Rules:
+- Rotate through all pillars across the week — don't stack the same pillar on consecutive days
+- Match format to channel norms (e.g. carousels for Instagram, long-form for LinkedIn, threads for X)
+- Opening hooks must be specific and scroll-stopping — no generic openers like "Did you know..."
+- Flag 1–2 posts per week as "High Priority" — these are the cornerstone pieces worth boosting or repurposing
+
+### 3. Repurposing Map
+
+For each "High Priority" post, add one repurposing suggestion — e.g. "Turn this LinkedIn article into a newsletter section" or "Clip this video for an Instagram Reel."
+
+## Quality Checks
+
+- [ ] Every week has balanced pillar distribution
+- [ ] No two consecutive posts have the same format on the same channel
+- [ ] Opening hooks are specific (no generic openers)
+- [ ] Formats match platform norms
+- [ ] Repurposing map covers all High Priority posts
+
+## Example Trigger Phrases
+
+- "Build me a 4-week content calendar for [brand]"
+- "Create a social media plan for [product launch]"
+- "Give me a monthly editorial calendar for my newsletter"
+- "Plan my LinkedIn content for the next month"
@@ -0,0 +1,78 @@
+---
+name: email-campaign
+description: "Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence."
+---
+
+# Email Campaign Skill
+
+This skill writes complete, sequenced email campaigns — from welcome flows to product launches to re-engagement sequences. Each email is written with subject line, preview text, full body copy, and CTA.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Campaign goal** (onboard new users / launch a product / nurture leads / re-engage churned users / announce a feature)
+- **Audience** (who receives this? job title, lifecycle stage, what they know already)
+- **Product or offer** being promoted or introduced
+- **Number of emails in sequence** (if unsure, recommend based on goal)
+- **Tone** (professional / conversational / bold / educational)
+- **Sender name** (person or brand?)
+
+## Sequence Recommendations by Goal
+
+If the user hasn't specified number of emails, use these defaults:
+- **Onboarding:** 4 emails over 7 days (Day 0, Day 1, Day 3, Day 7)
+- **Product launch:** 3 emails (Teaser → Launch Day → Follow-up/Last chance)
+- **Lead nurture:** 5 emails over 2 weeks
+- **Re-engagement:** 3 emails (Gentle nudge → Value reminder → Final offer)
+- **Feature announcement:** 2 emails (Announcement → How-to/deep dive)
+
+## Output Structure Per Email
+
+For every email in the sequence, produce:
+
+---
+
+**Email [N] of [Total] — [Descriptive label e.g. "Welcome / Day 0"]**
+**Send timing:** [When relative to trigger event or previous email]
+
+**Subject line:** [Primary option]
+**Subject line (A/B variant):** [Alternative to test]
+**Preview text:** [40–90 characters — adds context to the subject, doesn't repeat it]
+
+**Body:**
+
+[Full email copy — formatted with clear opening line, 2–3 body paragraphs, one primary CTA]
+
+**CTA button text:** [3–6 words]
+**CTA destination:** [What page/action this should link to]
+
+**Strategic note:** [Why this email does what it does — the psychological or strategic intent. 1–2 sentences.]
+
+---
+
+## Writing Rules
+
+- Opening line must earn attention — no "Hi, welcome to [product]" openers
+- Each email has ONE primary CTA — never two competing asks
+- Keep paragraphs to 2–3 sentences maximum for mobile readability
+- Use "you" more than "we" — centre the reader, not the brand
+- Subject lines under 50 characters perform best on mobile — flag if going over
+- Preview text should add information the subject doesn't — never just repeat it
+- Every email should stand alone — assume some subscribers miss earlier emails
+
+## Quality Checks
+
+- [ ] Each email has a single clear CTA
+- [ ] Subject lines are under 50 characters (or flagged)
+- [ ] Preview text doesn't repeat the subject line
+- [ ] Opening line is specific and attention-earning
+- [ ] Sequence has logical narrative arc (doesn't feel like disconnected blasts)
+- [ ] Tone is consistent across all emails
+- [ ] Strategic notes explain the intent of each email
+
+## Example Trigger Phrases
+
+- "Write a 3-email launch sequence for [product]"
+- "Build an onboarding email flow for [SaaS tool]"
+- "Create a drip campaign to nurture leads for [offer]"
+- "Write a re-engagement campaign for churned users"
@@ -0,0 +1,98 @@
+---
+name: go-to-market
+description: "Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Generates a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases."
+---
+
+# Go-To-Market Skill
+
+This skill produces a complete go-to-market asset pack for a product, feature, or initiative. It follows Geoffrey Moore's positioning framework and structures all outputs for use in sales decks, landing pages, launch emails, and internal alignment docs.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Product/feature name**
+- **One-line description** (what it does, technically)
+- **Target customer** (role, company size, industry if relevant)
+- **Primary problem it solves**
+- **Key competitor or alternative** (what people do today without this)
+- **Top 3 differentiators**
+
+## Output Structure
+
+Always produce all four sections below in order.
+
+---
+
+### 1. Positioning Statement
+
+Use the Geoffrey Moore format exactly:
+
+> For **[target customer]** who **[has this problem or need]**, **[Product Name]** is a **[product category]** that **[key benefit/outcome]**. Unlike **[primary alternative or competitor]**, our product **[key differentiator]**.
+
+Write one primary positioning statement, then offer a shorter tagline version (10 words or fewer) suitable for a hero headline.
+
+---
+
+### 2. Messaging Pillars
+
+Generate 3–5 messaging pillars. Each pillar must include:
+
+- **Pillar name** (2–4 words, bold)
+- **One-sentence summary** of what this pillar claims
+- **2–3 proof points** (specific, evidence-backed where possible — if the user hasn't provided data, flag with [ADD PROOF POINT])
+- **Example use in copy** (one sentence as it would appear in a landing page or deck)
+
+Pillars should be distinct — avoid overlap. Each pillar should be defensible against the primary competitor.
+
+---
+
+### 3. Feature & Functionality List
+
+Produce a two-column table:
+
+| Feature / Functionality | Buyer Benefit (what it means for the user) |
+|---|---|
+| [Technical capability] | [Outcome in plain language — start with a verb: "Reduces...", "Enables...", "Eliminates..."] |
+
+Rules:
+- Never list a feature without a corresponding benefit
+- Benefits should reference the target customer's workflow or pain point
+- Aim for 6–12 rows; ask the user for more features if they've only given 1–2
+- Avoid jargon in the benefit column — write as if explaining to a buyer, not an engineer
+
+---
+
+### 4. Use Cases
+
+Generate 3–5 role-specific use cases. Each use case must follow this format:
+
+**Use Case [N]: [Role] — [Scenario Title]**
+
+- **Who:** [Job title / role]
+- **Situation:** [The specific moment or trigger that leads them to use the product]
+- **Before:** [What they had to do without this product — be specific about time, friction, or risk]
+- **With [Product Name]:** [What they do now — concrete action, not vague benefit]
+- **Outcome:** [Measurable or tangible result]
+
+Use cases should cover different buyer personas if possible (e.g. end user, manager, admin).
+
+---
+
+## Quality Checks
+
+Before delivering output, verify:
+- [ ] Positioning statement follows Moore format exactly
+- [ ] Tagline is 10 words or fewer
+- [ ] Each pillar has at least 2 proof points (or flagged placeholders)
+- [ ] Every feature has a benefit — no orphaned features
+- [ ] Benefits start with action verbs
+- [ ] Use cases include a Before/After structure
+- [ ] Language is consistent with the target customer's vocabulary (not internal engineering terms)
+
+## Example Trigger Phrases
+
+- "Create a positioning statement for [product]"
+- "Write a GTM plan for [feature]"
+- "Give me key pillars for [product name]"
+- "Build a feature and use case list for [product]"
+- "We're launching [X] — help me with the messaging"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-people",
+  "version": "1.0.0",
+  "description": "Leadership & people skills: Performance Review, Hiring Rubric, Team Offsite Planner. Write structured reviews, build interview scorecards, and plan offsites from goals to minute-by-minute agenda.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "leadership", "management", "performance-review", "hiring", "interview", "offsite", "people"]
+}
@@ -0,0 +1,127 @@
+---
+name: hiring-rubric
+description: "Generate a structured interview scorecard and interview guide for any role. Use when asked to create a hiring rubric, interview scorecard, structured interview guide, or assessment criteria for a job. Produces a scorecard with competencies, behavioural questions, and scoring guidance."
+---
+
+# Hiring Rubric Skill
+
+This skill generates a complete structured interview scorecard and guide for any role. It reduces hiring bias, enables consistent evaluation across interviewers, and produces better hiring decisions.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Role title and level** (e.g. Senior Product Manager, Junior Data Analyst)
+- **Team or function** (e.g. Growth, Platform, Customer Success)
+- **Top 3–5 things this person needs to do well** (the actual job requirements, not just the JD)
+- **Interview format** (number of rounds, length of each)
+- **Any known gaps or risks to probe for** (optional)
+- **Company values or competencies** (optional — if provided, include as a competency section)
+
+## Output Structure
+
+---
+
+# Interview Scorecard: [Role Title]
+**Level:** [Junior / Mid / Senior / Staff / Manager]
+**Team:** [Team name]
+**Created:** [Date]
+
+---
+
+## Scorecard Overview
+
+Each competency is scored 1–4:
+- **4 — Strong Yes:** Clear evidence of exceptional ability. Hire signal.
+- **3 — Yes:** Solid evidence. Meets the bar for this role.
+- **2 — Lean No:** Some evidence but gaps that matter for this role.
+- **1 — No:** Little to no evidence. Clear miss.
+
+**Hiring recommendation:**
+- 3+ competencies at 4, rest at 3 = Strong hire
+- Majority at 3, no 1s = Hire
+- Any 1s or majority 2s = No hire (unless specific mitigating factors)
+
+---
+
+## Competencies & Scoring
+
+For each competency (generate 4–6 based on the role):
+
+### Competency [N]: [Name — e.g. "Problem Structuring" / "Stakeholder Influence" / "Technical Depth"]
+
+**Why this matters for this role:** [One sentence — connects to actual job requirements]
+
+**What 4 looks like (Strong Yes):**
+[Specific, observable behaviours. "Proactively decomposed an ambiguous problem into a structured approach without prompting. Could articulate tradeoffs clearly and made assumptions explicit."]
+
+**What 2 looks like (Lean No):**
+[Specific, observable behaviours at the lower end. "Could answer direct questions but struggled when the interviewer removed scaffolding. Required significant prompting to reach a structured answer."]
+
+**Interview Questions (2–3 per competency):**
+
+1. *[Behavioural STAR question — e.g. "Tell me about a time you had to make a decision with incomplete data."]*
+   - **Good answer signals:** [What a strong answer includes]
+   - **Weak answer signals:** [What a weak or scripted answer looks like]
+   - **Follow-up probe:** [One follow-up to push deeper]
+
+2. *[Situational or hypothetical question for this role]*
+   - **Good answer signals:**
+   - **Follow-up probe:**
+
+---
+
+## Role-Specific Technical Assessment (if applicable)
+
+[If the role requires a technical screen, describe:]
+- **Format:** [Take-home / Live coding / Case study / Portfolio review]
+- **Duration:** [Time]
+- **What you're assessing:** [Specific skills]
+- **Scoring guidance:** [What distinguishes a 4 from a 2 on the technical component]
+
+---
+
+## Culture & Values Assessment
+
+[2–3 values-based questions aligned to company values if provided, or general culture fit questions:]
+
+1. *[Question]*
+   - **What you're listening for:**
+
+---
+
+## Red Flags to Watch For
+
+[5–7 specific red flags relevant to this role and level:]
+- [e.g. "Speaks only about individual work — no mention of collaboration or team impact"]
+- [e.g. "Can't give a specific example — pivots to hypotheticals when asked for real situations"]
+- [e.g. "For senior roles: no evidence of influencing without authority"]
+
+---
+
+## Interview Panel Guide
+
+Suggest how to divide competencies across interview rounds to avoid repetition:
+
+| Round | Interviewer | Competencies to Assess |
+|---|---|---|
+| 1 — Recruiter Screen | Recruiter | Motivation, career narrative, basics |
+| 2 — Hiring Manager | [Role] | [Assign 2 competencies] |
+| 3 — Peer Interview | [Role] | [Assign 2 competencies] |
+| 4 — Stakeholder | [Role] | [Assign 1–2 competencies + culture] |
+
+---
+
+## Quality Checks
+
+- [ ] Scoring descriptions are observable (behaviours, not adjectives)
+- [ ] 4 vs 2 distinction is clear and specific
+- [ ] Questions have follow-up probes
+- [ ] Red flags are specific to this role and level
+- [ ] Panel guide avoids competency overlap between rounds
+
+## Example Trigger Phrases
+
+- "Create a hiring rubric for a [role]"
+- "Build an interview scorecard for [job title]"
+- "Give me structured interview questions for a [level] [role]"
+- "We're hiring a [role] — help me build an assessment framework"
@@ -0,0 +1,116 @@
+---
+name: performance-review
+description: "Write structured, balanced performance reviews from bullet-point inputs. Use when asked to write a performance review, self-assessment, peer review, 360 feedback, or manager evaluation. Produces a complete, fair, professionally written review covering achievements, areas for growth, and development goals."
+---
+
+# Performance Review Skill
+
+This skill turns rough notes, bullet points, or bullet-point memories into a complete, professionally written performance review. Output is ready to submit or use as a strong first draft.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Review type** (Self-assessment / Manager review / Peer/360 / Upward feedback)
+- **Review period** (e.g. H1 2025, Q2 2025, Annual)
+- **Name of person being reviewed** (or "myself" for self-assessment)
+- **Role / level**
+- **Key achievements or notable work** (rough notes are fine)
+- **Areas where they struggled or could improve** (be honest — reviews without growth areas aren't credible)
+- **Key projects or deliverables from the period**
+- **Company values or competencies to assess against** (optional — if provided, structure the review around them)
+- **Overall rating/recommendation** (if the form requires one)
+
+## Output Structure
+
+---
+
+# Performance Review: [Name]
+**Role:** [Title / Level]
+**Review period:** [Period]
+**Review type:** [Manager / Self / Peer / Upward]
+**Reviewed by:** [If known]
+
+---
+
+## Overall Summary
+
+[3–5 sentences. High-level characterisation of the period. Acknowledge standout contributions. Be specific — use project names and outcomes, not vague praise. For self-assessments, this should reflect honestly on the period without underselling or overselling.]
+
+---
+
+## Achievements & Impact
+
+[3–5 achievements, each structured as:]
+
+**[Achievement title — specific and concrete]**
+[2–4 sentences. What was the context? What did [name] do specifically? What was the measurable or observable outcome? Avoid generic praise — every sentence should be something only this person could have done.]
+
+---
+
+## Strengths Demonstrated
+
+[3–4 bullet points. Each bullet = one strength, with one concrete example from the review period. No abstract traits without evidence.]
+
+- **[Strength]:** [Example — specific project or behaviour that demonstrated this]
+
+---
+
+## Areas for Growth
+
+[2–3 areas. Be direct and constructive — not vague. Frame as "opportunity to develop" not "failure." Each should include:]
+
+**[Area name]**
+- **Observed pattern:** [What was noticed — be specific, not personal]
+- **Why it matters:** [Impact on team, output, or career progression]
+- **Suggested development:** [One concrete action — e.g. "Take on [X] responsibility next half" or "Shadow [role] on [process]"]
+
+---
+
+## Development Goals for Next Period
+
+[2–3 goals. Format each as:]
+
+**Goal [N]:** [Clear, outcome-oriented goal]
+- **Why:** [Connection to growth areas or career aspirations]
+- **How to measure:** [What "done" looks like]
+- **Support needed:** [Resources, training, or manager input required]
+
+---
+
+## Competency Ratings (if framework provided)
+
+| Competency | Rating | Evidence |
+|---|---|---|
+| [Competency from company framework] | [Exceeds / Meets / Developing / Below] | [One-sentence example] |
+
+---
+
+## Closing Recommendation
+
+[2–3 sentences. For manager reviews: overall assessment and any promotion/compensation recommendation. For self-assessments: what you're asking for or committing to. For peer reviews: one sentence on what it's like to work with this person.]
+
+---
+
+## Writing Rules
+
+- Never use vague phrases: "strong communicator," "team player," "hardworking" — always back with evidence
+- Growth areas must be honest — reviewers who only write positives lose credibility and help no one
+- Use third person for manager/peer reviews, first person for self-assessments
+- Avoid jargon — "drove alignment" and "leveraged synergies" are meaningless. Use plain language.
+- If the user gives sparse notes, ask for one concrete example per achievement before writing
+
+## Quality Checks
+
+- [ ] Every achievement includes a specific outcome (not just activity)
+- [ ] Strengths have concrete examples from the review period
+- [ ] Growth areas are honest and constructive (not softened to meaninglessness)
+- [ ] Development goals are measurable
+- [ ] No vague phrases without evidence
+- [ ] Tone is professional and fair throughout
+
+## Example Trigger Phrases
+
+- "Write a performance review for [name] based on these notes: [paste notes]"
+- "Help me write my self-assessment for [period]"
+- "Draft a peer review for my colleague who did [description]"
+- "Turn these bullet points into a full performance review: [paste bullets]"
@@ -0,0 +1,144 @@
+---
+name: team-offsite-planner
+description: "Plan a team offsite from goals to full agenda. Use when asked to plan a team offsite, away day, team retreat, quarterly offsite, or team-building event. Produces a full agenda, session designs, facilitation notes, and logistics checklist."
+---
+
+# Team Offsite Planner Skill
+
+This skill designs a complete team offsite — from goals to minute-by-minute agenda, including session facilitation guides and a logistics checklist.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Team size** (number of people)
+- **Duration** (half day / full day / 1.5 days / 2 days)
+- **Primary goal** (e.g. Q3 planning / team bonding / strategy alignment / retrospective / all of the above)
+- **Location type** (office / external venue / remote-first hybrid)
+- **Key topics to cover** (if known)
+- **Any constraints** (budget, accessibility, team dynamics to be aware of)
+- **Remote attendees?** (Yes/No — affects session design significantly)
+
+## Output Structure
+
+---
+
+# Team Offsite Plan: [Team Name]
+**Date:** [TBD or as provided]
+**Duration:** [X days]
+**Attendees:** [X people]
+**Goal:** [Primary goal from inputs]
+
+---
+
+## 1. Offsite Objectives
+
+State 3–5 clear objectives. Each objective should be answerable at the end of the offsite — the team should be able to say "we achieved this" or "we didn't."
+
+- By the end of this offsite, we will have [specific outcome].
+
+---
+
+## 2. Full Agenda
+
+For each time block, produce:
+
+**[Time] — [Session Title]** *(Duration: X min)*
+- **Type:** [Opening / Working session / Workshop / Decision / Social / Break]
+- **Owner:** [Who runs this — Facilitator / Specific person / Group]
+- **Goal:** [What this session produces or achieves]
+- **Format:** [How it runs — e.g. "Whole group discussion", "4 breakout groups of 3", "Silent async doc read + Q&A"]
+- **Output:** [What leaves the room — e.g. "Agreed list of H2 priorities", "Updated team norms doc", "Go/No-go decision on X"]
+
+---
+
+**Day 1 Example Structure:**
+
+| Time | Session | Duration | Type |
+|---|---|---|---|
+| 09:00 | Arrival & coffee | 30 min | Social |
+| 09:30 | Opening & objectives | 20 min | Framing |
+| 09:50 | [Strategic session 1] | 90 min | Working |
+| 11:20 | Break | 15 min | — |
+| 11:35 | [Workshop or decision] | 75 min | Workshop |
+| 13:00 | Lunch | 60 min | Social |
+| 14:00 | [Working session 2] | 90 min | Working |
+| 15:30 | Break | 15 min | — |
+| 15:45 | [Team session / retro] | 60 min | Team |
+| 16:45 | Day close — commitments | 30 min | Close |
+| 17:15 | Social / dinner | Open | Social |
+
+Adapt timing to duration and goals.
+
+---
+
+## 3. Session Facilitation Notes
+
+For each working session, provide:
+
+### Session: [Name]
+
+**Time needed:** [X minutes]
+**Materials:** [Post-its, Miro board, printed docs, etc.]
+
+**Step-by-step facilitation:**
+1. [What the facilitator says/does to open — 2–3 min]
+2. [Core activity — describe in detail]
+3. [How to gather/consolidate output]
+4. [Closing move — decision, vote, or commitment]
+
+**If the group gets stuck:** [One facilitation technique to unstick — e.g. "Dot voting if no consensus", "Parking lot for off-topic items"]
+
+**Watch out for:** [Common pitfall for this session type — e.g. "The loudest voices dominating. Use silent individual writing first."]
+
+---
+
+## 4. Pre-Offsite Prep Checklist
+
+For the organiser to complete before the offsite:
+
+**2 weeks before:**
+- [ ] Book venue and confirm capacity and AV
+- [ ] Send calendar invites with travel info
+- [ ] Share pre-read or pre-work doc (if any)
+- [ ] Confirm dietary requirements and accessibility needs
+
+**1 week before:**
+- [ ] Send agenda to all attendees
+- [ ] Assign session owners and brief them
+- [ ] Prepare materials (print, Miro boards, name cards)
+- [ ] Confirm remote setup if hybrid
+
+**Day before:**
+- [ ] Test AV and video conferencing setup
+- [ ] Prepare room layout
+- [ ] Confirm headcount and catering
+
+---
+
+## 5. Post-Offsite Actions
+
+Template for the summary document to send within 48 hours:
+
+**[Team] Offsite Summary — [Date]**
+- **Decisions made:** [List]
+- **Actions and owners:** [Table: Action | Owner | Due date]
+- **Parking lot items:** [Topics deferred for follow-up]
+- **Next check-in:** [When the team will review offsite commitments]
+
+---
+
+## Quality Checks
+
+- [ ] Objectives are measurable at end of day
+- [ ] Sessions alternate between high-energy and reflective
+- [ ] No single session runs longer than 90 minutes without a break
+- [ ] Remote attendees have equal participation in working sessions
+- [ ] Each working session has a stated output
+- [ ] Agenda has social/informal time built in
+
+## Example Trigger Phrases
+
+- "Plan a 1-day offsite for my team of [size]"
+- "Design a 2-day team retreat for [goal]"
+- "Build an agenda for our Q[N] team planning day"
+- "Help me plan a hybrid offsite for [team size] people"
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-planning",
+  "version": "3.0.0",
+  "description": "Planning & strategy skills: OKR Builder, Feature Prioritisation (RICE/MoSCoW/Kano/ICE), Roadmap Presentation, Pricing Strategy, RICE + Impact Matrix, Roadmap Narrative.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "okr", "prioritisation", "roadmap", "pricing", "rice", "moscow", "kano"]
+}
@@ -0,0 +1,104 @@
+---
+name: feature-prioritisation
+description: Applies prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs. Triggers on "prioritise features", "what should we build", "backlog grooming", "RICE score", "MoSCoW".
+---
+
+# Feature Prioritisation Skill
+
+Apply the right prioritisation framework to any backlog and produce a clear, defensible ranking with rationale — not just a sorted list.
+
+## Framework Selection Guide
+
+Ask the user which framework they prefer, or recommend based on context:
+
+| Situation | Recommended Framework |
+|---|---|
+| Need a quick, data-driven score | RICE |
+| Stakeholder alignment meeting | MoSCoW |
+| Understanding customer delight vs expectations | Kano |
+| Early-stage startup, fast decisions | ICE |
+| Identifying underserved customer needs | Opportunity Scoring |
+| Strategic portfolio decisions | Value vs Effort Matrix |
+
+---
+
+## RICE Scoring
+
+**Formula:** (Reach × Impact × Confidence) ÷ Effort
+
+| Factor | Definition | Scale |
+|---|---|---|
+| Reach | Users impacted per quarter | Actual number |
+| Impact | Effect on goal per user | 0.25 / 0.5 / 1 / 2 / 3 |
+| Confidence | How certain are you? | 50% / 80% / 100% |
+| Effort | Person-months required | Actual number |
+
+Output table:
+| Feature | Reach | Impact | Confidence | Effort | RICE Score | Priority |
+|---|---|---|---|---|---|---|
+
+---
+
+## MoSCoW Method
+
+Categorise each feature as:
+- **Must Have** — non-negotiable for launch/sprint; product fails without it
+- **Should Have** — important but not critical; workarounds exist
+- **Could Have** — nice to have; include only if time allows
+- **Won't Have (this time)** — explicitly out of scope now; may revisit
+
+Always ask: "Must have for *what*?" — define the scope (launch, sprint, quarter) before categorising.
+
+---
+
+## ICE Scoring (Startup/fast mode)
+
+**Formula:** Impact + Confidence + Ease (each 1–10)
+
+Quick, subjective — good for early decisions before data exists.
+
+---
+
+## Kano Model
+
+Classify features into:
+- **Basic (Must-be):** Expected; absence causes dissatisfaction
+- **Performance:** More = better satisfaction; linear relationship
+- **Excitement (Delighters):** Unexpected; creates delight; absence is neutral
+- **Indifferent:** Users don't care either way
+- **Reverse:** Some users want it, others don't
+
+Recommend building: all Basic features first → Performance features for key use cases → 1–2 Excitement features per release.
+
+---
+
+## Output Format
+
+### Feature Prioritisation — [Product/Team] — [Date]
+
+**Framework Used:** [RICE / MoSCoW / ICE / Kano / Custom]
+**Scope:** [Sprint / Quarter / Release]
+**Goal being prioritised against:** [Metric or objective]
+
+[Scored table using selected framework]
+
+**Recommended Build Order:**
+1. [Feature] — [1-line rationale]
+2. [Feature] — [1-line rationale]
+3. ...
+
+**Explicitly Deprioritised:**
+- [Feature] — Reason: [brief]
+
+**Assumptions Made:**
+- [Any estimates or judgements used in scoring]
+
+---
+
+## Guidelines
+
+- Always anchor prioritisation to a specific goal or metric — never prioritise in a vacuum
+- Flag when two features have similar scores but very different risk profiles
+- If stakeholder politics are influencing prioritisation, name it explicitly and suggest separating the framework score from the final decision
+- Recommend revisiting priorities every 2 weeks minimum
+- Never produce a single-column ranked list without rationale — explain the top 3 and bottom 3 decisions
@@ -0,0 +1,69 @@
+---
+name: okr-builder
+description: Creates well-structured OKRs (Objectives and Key Results) for product teams, startups, and individuals. Use when asked to write OKRs, set quarterly goals, define key results, or review existing OKRs. Triggers on "OKR", "objective and key results", "quarterly goals", "north star metric".
+---
+
+# OKR Builder Skill
+
+Write ambitious, measurable OKRs that connect product work to company strategy. Avoid vanity metrics, output-focused key results, and objectives that sound like task lists.
+
+## OKR Fundamentals
+
+**Objective:** Qualitative, inspiring, time-bound. Answers "where are we going?"
+**Key Result:** Quantitative, specific, measurable. Answers "how will we know we've arrived?"
+
+### The Test for a Good KR
+- Can it be scored 0.0–1.0 at the end of the period?
+- Does it measure outcome, not output? ("Revenue from new customers increased by 30%" not "Launch 3 features")
+- Is it ambitious but achievable? (Aim for 70% attainment as the gold standard)
+- Is it within the team's control?
+
+## Common OKR Anti-Patterns to Flag and Fix
+
+| Anti-Pattern | Example | Better Version |
+|---|---|---|
+| Task masquerading as KR | "Launch onboarding redesign" | "New user activation rate increases from 42% to 65%" |
+| Vanity metric | "Get 10,000 app downloads" | "30-day retention for new users reaches 40%" |
+| Binary KR | "Ship API v2" | "API v2 adopted by 80% of active integrations" |
+| Too many KRs | 6+ per objective | Max 3–4 KRs per objective |
+| No baseline | "Improve NPS" | "NPS increases from 32 to 50" |
+
+Always flag anti-patterns and offer a rewrite.
+
+## Output Format
+
+### [Quarter] OKRs — [Team/Product Area]
+
+---
+
+**Objective 1: [Inspiring, qualitative statement]**
+
+*Why this matters:* [1–2 sentence strategic context]
+
+| # | Key Result | Baseline | Target | Measurement Method |
+|---|---|---|---|---|
+| KR1 | [Measurable outcome] | [Current state] | [Target] | [How measured] |
+| KR2 | [Measurable outcome] | [Current state] | [Target] | [How measured] |
+| KR3 | [Measurable outcome] | [Current state] | [Target] | [How measured] |
+
+*Owner:* [Name/Role]
+*Check-in cadence:* Weekly
+
+---
+
+Repeat for each objective. Recommend 2–4 objectives per team per quarter.
+
+## Scoring Guide to Include
+
+At quarter end, score each KR:
+- 0.7–1.0 = Excellent (0.7 is the "sweet spot" — if all KRs score 1.0, they weren't ambitious enough)
+- 0.4–0.6 = Made progress but missed
+- 0.0–0.3 = Missed — needs retrospective discussion
+
+## Guidelines
+
+- Always ask for the company-level or product-level North Star metric before writing OKRs
+- Recommend no more than 3 objectives per team per quarter
+- If user provides output-based goals, always reframe as outcomes
+- Include a "health check" section flagging which KRs have no current baseline data
+- Remind user: OKRs are not performance reviews — they should be ambitious enough that missing them is okay
@@ -0,0 +1,118 @@
+---
+name: pricing-strategy
+description: Structures pricing strategy decisions, packaging options, and pricing page design for SaaS and digital products. Use when reviewing or setting pricing, designing pricing tiers, evaluating freemium vs paid, or preparing a pricing change. Triggers on "pricing strategy", "pricing tiers", "freemium", "pricing page", "how should we price", "pricing change".
+---
+
+# Pricing Strategy Skill
+
+Build pricing that reflects value delivered — not cost to build. Structure every pricing decision with customer segmentation, value metric identification, competitive context, and a packaging recommendation.
+
+## Pricing Foundations
+
+Three questions to answer before any pricing decision:
+1. **Who is our buyer?** (Role, company size, willingness to pay)
+2. **What value do we deliver?** (Quantifiable outcome — time saved, revenue generated, risk reduced)
+3. **What is our pricing model?** (Per seat, usage-based, flat, hybrid)
+
+---
+
+## Pricing Models
+
+| Model | Best For | Risk |
+|---|---|---|
+| **Per Seat** | Collaboration tools, team software | Disincentivises adoption as team grows |
+| **Usage-Based** | APIs, infrastructure, consumption tools | Revenue unpredictability for both sides |
+| **Flat Rate** | Simple tools, early-stage | Leaves money on table from power users |
+| **Tiered** | Products with clear user segments | Feature gatekeeping frustrates users |
+| **Freemium** | Viral/PLG products with low marginal cost | Conversion to paid is hard to engineer |
+| **Value-Based** | Enterprise, outcomes-driven products | Requires strong ROI story |
+
+---
+
+## Freemium Decision Framework
+
+Use freemium when:
+- ✅ Marginal cost per free user is near zero
+- ✅ Product is inherently viral (network effects or sharing)
+- ✅ Free tier creates genuine value (not just a demo)
+- ✅ Clear upgrade trigger exists (feature, volume, or team size)
+- ✅ Conversion benchmark is realistic (2–5% free-to-paid is typical)
+
+Avoid freemium when:
+- ❌ Support cost per free user is high
+- ❌ No natural upgrade trigger in the product
+- ❌ Core value requires features you'd need to gate
+
+---
+
+## Packaging / Tiering Framework
+
+Recommended 3-tier structure for SaaS:
+
+| Tier | Target | Price Signal | Key Features | Lock-in Mechanism |
+|---|---|---|---|---|
+| **Free / Starter** | Individual, early discovery | $0 | Core value, usage-limited | Invite colleagues, export limit |
+| **Pro / Growth** | SMB, growing teams | $[X]/seat/mo | Full features, higher limits | Team collaboration, integrations |
+| **Business / Enterprise** | Mid-market, enterprise | $[X]/seat/mo or custom | Admin, SSO, SLAs, dedicated support | Security, compliance, volume |
+
+Tier design rules:
+- Each tier should be genuinely sufficient for its target segment
+- The upgrade trigger should be felt naturally — not manufactured
+- Price jumps of 3–5x between tiers are normal and defensible
+
+---
+
+## Competitive Pricing Context
+
+| Competitor | Model | Price | Key Differentiator |
+|---|---|---|---|
+| [Name] | [Model] | [Price] | [What they lead with] |
+
+Positioning options:
+- **Premium:** Price 20–40% above market. Justify with enterprise features, support, or brand.
+- **Parity:** Match the market leader. Win on product or distribution.
+- **Value:** Price below market. Win on volume. Dangerous without strong unit economics.
+
+---
+
+## Output Format
+
+### Pricing Strategy Recommendation — [Product] — [Date]
+
+**Current State:** [What pricing exists today, if any]
+**Problem to Solve:** [Why pricing is being reviewed]
+
+**Recommended Pricing Model:** [Model name + rationale]
+
+**Value Metric:** [The single unit that scales with customer value — e.g., "active users", "API calls", "documents processed"]
+
+**Proposed Tiers:**
+
+[Table using 3-tier structure above]
+
+**Free-to-Paid Upgrade Trigger:** [Specific moment or threshold that creates natural upgrade pressure]
+
+**Competitive Position:** [Premium / Parity / Value + reasoning]
+
+**Pricing Change Rollout (if applicable):**
+- Grandfathering: [Yes / No — recommendation and rationale]
+- Communication plan: [How to tell customers + timing]
+- Rollback plan: [Under what conditions you'd revert]
+
+**Risks:**
+- [Risk] → Mitigation: [Action]
+
+**Metrics to Monitor Post-Change:**
+- Conversion rate (free to paid)
+- Churn rate by tier
+- Average revenue per user (ARPU)
+- Expansion revenue
+
+---
+
+## Guidelines
+
+- Never price based on cost — price based on value delivered to the customer
+- Always A/B test price changes where possible; use geographic holdouts if A/B isn't feasible
+- Recommend annual pricing with 15–20% discount — improves cash flow and reduces churn
+- If enterprise pricing is "contact us", recommend adding a price floor to qualify inbound
@@ -0,0 +1,44 @@
+---
+name: rice-impact-matrix
+description: Score features using RICE and plot against strategic alignment for nuanced prioritisation
+tool_integration: Miro, Jira
+---
+# RICE + Strategic Alignment Skill
+
+## Purpose
+Produce a prioritisation output that balances quantitative RICE scoring with qualitative strategic fit — because the highest RICE score isn't always the right next bet.
+
+## Two-Stage Process
+
+### Stage 1: RICE Scoring
+- Reach: Users affected per quarter
+- Impact: 3/2/1/0.5/0.25 scale
+- Confidence: 100% / 80% / 50%
+- Effort: Person-months
+- RICE = (R × I × C) / E
+
+### Stage 2: Strategic Alignment Score
+Rate each initiative against your current strategic priorities (provide these as input):
+- Directly supports top OKR: +3
+- Supports secondary OKR: +2
+- Neutral: +1
+- Contradicts strategic direction: -1
+
+### Final Priority Score
+Combined Score = RICE Score + (Strategic Alignment × 10)
+
+## Output Format
+
+### Priority Matrix — [Quarter]
+| Initiative | RICE Score | Strategic Alignment | Combined Score | Quadrant | Recommendation |
+|------------|------------|--------------------|--------------------|----------|----------------|
+| [name] | [score] | [score] | [combined] | [Now/Next/Later/Drop] | [action] |
+
+#### Quadrant Definitions
+- **Now:** High RICE + High Strategic Alignment → Build this quarter
+- **Next:** High RICE + Lower Alignment → Queue for next quarter
+- **Later:** Lower RICE + High Alignment → Revisit when capacity allows
+- **Drop:** Low RICE + Low Alignment → Remove from backlog
+
+#### Recommendations
+[Top 5 initiatives with rationale for sequencing]
@@ -0,0 +1,39 @@
+---
+name: rice-prioritisation
+description: Score and rank product initiatives using the RICE framework
+tool_integration: Jira
+---
+# RICE Prioritisation Skill
+
+## Purpose
+Apply consistent, criteria-based RICE scoring to a list of features or initiatives to produce an objective prioritisation ranking.
+
+## RICE Definitions (adapt to your context)
+- **Reach:** Number of users affected per quarter (use actual DAU/MAU data where available)
+- **Impact:** Effect on your primary metric — use scale: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal
+- **Confidence:** How certain are we about R and I estimates? 100%=high, 80%=medium, 50%=low
+- **Effort:** Person-months required across all functions
+
+## RICE Formula
+RICE Score = (Reach × Impact × Confidence) / Effort
+
+## Process
+1. For each initiative provided, gather or estimate R, I, C, E values
+2. Flag where estimates are weak and note what data would improve them
+3. Calculate RICE score for each
+4. Rank highest to lowest
+5. Flag any "quick wins" (high RICE score, low effort) and "moonshots" (high impact, high effort)
+6. Note dependencies between items that affect sequencing
+
+## Output Format
+
+### RICE Prioritisation: [Backlog/Quarter]
+| Initiative | Reach | Impact | Confidence | Effort | RICE Score | Notes |
+|------------|-------|--------|------------|--------|------------|-------|
+| [name] | [n] | [score] | [%] | [months] | [score] | [flags] |
+
+#### Recommended Sequence
+[Top 5 initiatives with rationale]
+
+#### Data Gaps to Address
+[What information would most improve scoring accuracy]
@@ -0,0 +1,37 @@
+---
+name: roadmap-narrative
+description: Transform a prioritised initiative list into a compelling strategic roadmap narrative
+tool_integration: Notion, Miro
+---
+# Roadmap Narrative Skill
+
+## Purpose
+Convert a ranked list of product initiatives into a clear, strategic narrative that connects individual items to company goals and communicates a coherent product direction.
+
+## Process
+1. Review the prioritised initiative list and company OKRs provided
+2. Identify 2-3 strategic themes that group the initiatives naturally
+3. For each theme, articulate: the problem it addresses, the customer it serves, the metric it moves
+4. Write a quarter-level narrative that shows progression — how does H1 set up H2?
+5. Draft an executive summary (3-4 sentences max) that non-technical stakeholders can repeat
+
+## Output Format
+
+### Product Roadmap: [Quarter/Half/Year]
+**Strategic Context:** [1 paragraph: market moment, key challenge, our response]
+
+#### Theme 1: [Theme Name]
+- Strategic rationale
+- Initiatives included
+- Primary metric impacted
+- Dependencies
+
+[Repeat for each theme]
+
+**Executive Summary (shareable):**
+[3-4 sentences that could be shared in an all-hands or board update]
+
+## Tone Guidelines
+- Avoid jargon — write for a CFO, not an engineer
+- Lead with customer outcomes, not features
+- Be honest about what's NOT on the roadmap and why
@@ -0,0 +1,114 @@
+---
+name: roadmap-presentation
+description: Creates structured roadmap presentations and narratives for executive, stakeholder, and team audiences. Use when asked to build a product roadmap, present roadmap to leadership, create a roadmap slide, or communicate quarterly plans. Triggers on "roadmap presentation", "product roadmap", "quarterly roadmap", "roadmap slide", "roadmap for leadership".
+---
+
+# Roadmap Presentation Skill
+
+Build roadmaps that tell a strategy story — not just a list of features with dates. Every roadmap output is audience-calibrated: executives get outcomes, teams get specificity, customers get value.
+
+## Audience Calibration
+
+Always ask who the audience is before building:
+
+| Audience | They care about | Format |
+|---|---|---|
+| **Executive / Board** | Business outcomes, revenue, risk, strategic alignment | Outcome-led, 3 columns (Now / Next / Later), no sprint detail |
+| **Cross-functional stakeholders** | Dependencies, timelines, their team's involvement | Theme-based, with dependency callouts |
+| **Engineering team** | Specificity, sequencing, technical constraints | Detailed, with epics and rough sizing |
+| **Customers / External** | Value delivered, no internal detail | Benefits-focused, no dates — "Coming soon / In progress / Done" |
+
+---
+
+## The Now / Next / Later Framework
+
+Standard output structure:
+
+**NOW** (Current quarter — high confidence, committed)
+- What we're building and why
+- Expected outcomes
+
+**NEXT** (Following quarter — medium confidence, directional)
+- Themes and initiatives
+- Key hypotheses being tested
+
+**LATER** (6–12 months — low confidence, aspirational)
+- Strategic bets
+- Dependencies that need to resolve first
+
+⚠️ Never put specific dates on "Later" items. Use quarters or halves.
+
+---
+
+## Roadmap Narrative Template
+
+Every roadmap needs a narrative, not just a timeline. Structure it as:
+
+1. **Where we are** — current product state and key metrics
+2. **The problem we're solving** — what's holding customers or the business back
+3. **Our strategic bets** — the themes that guide this roadmap
+4. **What we're building** — Now / Next / Later breakdown
+5. **How we'll know it's working** — success metrics per theme
+6. **What we're not doing** — explicit deprioritisation with rationale
+
+---
+
+## Output Format
+
+### Product Roadmap — [Product Area] — [Quarter/Year]
+
+**Audience:** [Executive / Team / Customer]
+**Roadmap Owner:** [PM Name]
+**Last Updated:** [Date]
+**Confidence Level:** Now = High | Next = Medium | Later = Low
+
+---
+
+**Strategic Context:**
+> [2–3 sentences: what company/product goal does this roadmap serve?]
+
+**Guiding Themes This Period:**
+1. [Theme 1] — [1-line rationale]
+2. [Theme 2] — [1-line rationale]
+3. [Theme 3] — [1-line rationale]
+
+---
+
+**NOW — [Quarter]**
+
+| Theme | Initiative | Outcome Expected | Team | Status |
+|---|---|---|---|---|
+| [Theme] | [What we're building] | [Metric it moves] | [Owner] | In Progress / Starting |
+
+**NEXT — [Quarter]**
+
+| Theme | Initiative | Hypothesis | Dependencies |
+|---|---|---|---|
+| [Theme] | [What we plan to build] | [If we build X, we expect Y] | [What needs to be true first] |
+
+**LATER — [H2 / Next Year]**
+
+| Theme | Strategic Bet | Why Later |
+|---|---|---|
+| [Theme] | [What we might build] | [What's blocking or uncertain] |
+
+---
+
+**What We're NOT Building (and Why):**
+- [Requested initiative] — Deprioritised because: [reason]
+- [Requested initiative] — Deprioritised because: [reason]
+
+**Success Metrics for This Roadmap:**
+| Metric | Now Target | End of Year Target |
+|---|---|---|
+| [Metric] | [X] | [Y] |
+
+---
+
+## Guidelines
+
+- Never let a roadmap become a commitment list — frame everything outside "Now" as directional
+- Always include a "not doing" section — it prevents the roadmap from becoming a wish list in disguise
+- For executive audiences: lead with the outcome the roadmap delivers to the business, not the features
+- Recommend a roadmap review cadence: monthly for Now items, quarterly for Next/Later
+- If dates are demanded for Later items: use quarters (Q3 2026), not specific dates
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-rituals",
+  "version": "3.0.0",
+  "description": "PM Weekly Review: a 20-minute structured ritual covering metrics movement, shipping progress, customer insights, and next week's top 3 priorities in a shareable update.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "weekly-review", "productivity", "rituals", "planning"]
+}
@@ -0,0 +1,107 @@
+---
+name: pm-weekly-review
+description: Structures a PM's weekly review and planning session — synthesising metrics, shipping progress, blockers, and next-week priorities into a shareable update. Use when doing a weekly PM review, writing a weekly update, preparing for a Monday planning session, or reviewing sprint health. Triggers on "weekly review", "weekly update", "PM standup", "weekly planning", "end of week summary".
+---
+
+# PM Weekly Review Skill
+
+Turn the chaotic end-of-week brain dump into a structured 20-minute ritual that keeps you, your team, and your stakeholders aligned — without a meeting.
+
+## The Weekly Review Structure (20 minutes)
+
+**5 min — Metrics check:** What moved? What didn't? What's surprising?
+**5 min — Ship progress:** What shipped? What slipped? What's blocked?
+**5 min — Insights:** Any customer feedback, support tickets, or research findings?
+**5 min — Next week priorities:** What are the 3 things that matter most?
+
+---
+
+## Output Format
+
+### PM Weekly Review — Week of [Date]
+
+**Product Area:** [What you own]
+**Written by:** [PM Name]
+**Time to read:** ~3 minutes
+
+---
+
+### 📊 Metrics This Week
+
+| Metric | This Week | Last Week | Target | Trend |
+|---|---|---|---|---|
+| [Primary metric] | [Value] | [Value] | [Target] | ↑ / ↓ / → |
+| [Secondary metric] | [Value] | [Value] | [Target] | ↑ / ↓ / → |
+| [Health metric] | [Value] | [Value] | [Target] | ↑ / ↓ / → |
+
+**Notable movement:**
+- [What changed and why — 1 sentence each]
+
+**Concern to watch:**
+- [Anything trending in the wrong direction]
+
+---
+
+### 🚢 This Week's Progress
+
+**Shipped:**
+- ✅ [What went live] — [1-line impact or observation]
+
+**In Progress:**
+- 🔄 [Feature/initiative] — [% complete or current status]
+
+**Slipped / Blocked:**
+- ⚠️ [What didn't happen] — Reason: [brief] — Action: [who's unblocking it]
+
+**Carry-forward to next week:**
+- [Item + why it's carrying over]
+
+---
+
+### 💡 Insights & Signals
+
+**Customer feedback:**
+- "[Quote or paraphrase]" — Source: [user/channel] — Theme: [tag]
+
+**Support signals:**
+- [Top ticket category this week + volume]
+- [Anything that signals a product gap]
+
+**Research / data:**
+- [Any discovery from user interviews, analytics, or experiments]
+
+---
+
+### 🎯 Next Week — Top 3 Priorities
+
+| # | Priority | Why This Week | Owner | Done = |
+|---|---|---|---|---|
+| 1 | [Most important thing] | [Reason it can't wait] | [Name] | [Clear definition of done] |
+| 2 | [Second priority] | [Why] | [Name] | [Done criteria] |
+| 3 | [Third priority] | [Why] | [Name] | [Done criteria] |
+
+**Decisions needed:**
+- [Any decision that's blocking progress — who needs to make it]
+
+**Asks / dependencies:**
+- [What you need from engineering / design / data / leadership]
+
+---
+
+### 🧠 Reflection (Optional but powerful)
+
+> What's one thing from this week I'd do differently?
+> [Your honest answer — 1–2 sentences]
+
+> What's the biggest unknown I'm carrying into next week?
+> [Name the uncertainty explicitly]
+
+---
+
+## Guidelines
+
+- Keep the whole document under 400 words — if stakeholders won't read it, it doesn't exist
+- The reflection section is for you, not your stakeholders — keep it honest
+- Always name a clear owner for every blocked item — "the team will figure it out" is a blocker in disguise
+- Recommend sending this by end of Friday — Monday morning is too late to course-correct
+- If three weeks of weekly reviews show the same blocked item, escalate immediately
@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-strategy",
+  "version": "3.0.0",
+  "description": "Strategy & stakeholder skills: Competitor Signal Tracker, Competitive Intelligence Monitor, Stakeholder Influence Mapper, Strategic Narrative Generator, Executive Update, Ambiguity Resolver.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["product-management", "strategy", "competitive-intelligence", "stakeholder", "executive", "narrative"]
+}
@@ -0,0 +1,67 @@
+---
+name: ambiguity-resolver
+description: Structures vague opportunities and unclear briefs into actionable 
+one-page problem statements. Use when user has a vague brief, undefined problem, 
+unclear opportunity, or says "we need to figure out what to do about X", "can 
+you help me make sense of this", or "I've been asked to look into Y".
+metadata:
+  author: Mohit Aggarwal
+  version: 1.0.0
+  category: discovery
+  tags: [discovery, strategy, problem-framing, ambiguity]
+  documentation: https://github.com/mohitagw15856/pm-claude-skills
+---
+# Ambiguity Resolver Skill
+
+## Purpose
+Turn vague briefs and half-formed opportunities into structured, actionable 
+problem statements — so you can reply with clarity instead of asking for three 
+more meetings.
+
+## Three-Stage Process
+
+### Stage 1: Reframe
+- Restate the vague input as 3-5 explicit questions that need answering
+- Identify the unstated assumptions hidden in the brief
+- Surface the real decision this feeds into (what will someone do differently 
+  once this is resolved?)
+
+### Stage 2: Scope
+- Define what is explicitly IN scope
+- Define what is explicitly OUT of scope (equally important)
+- Identify the deadline pressure: is this urgent/important, important/not urgent,
+  or unclear?
+- Name who owns the final decision and who needs to be consulted
+
+### Stage 3: Action
+- Define the minimum viable research: 2-3 activities maximum that would give 
+  enough signal to move forward with confidence
+- Time estimate for each activity
+- What each activity would tell you (and what it wouldn't)
+- Proposed check-in point: when to regroup before committing to more
+
+## Output Format
+
+### Problem Brief: [Opportunity Area]
+
+**Restated as questions:**
+1. [Question 1]
+2. [Question 2]
+3. [Question 3]
+
+**Unstated assumptions we should surface:**
+- [Assumption 1]
+- [Assumption 2]
+
+**In scope:** [Clear boundary]
+**Out of scope:** [Clear boundary]
+**Decision owner:** [Name/role]
+**Timeline:** [Real deadline if known, or "unclear — recommend setting one"]
+
+**Minimum viable research:**
+| Activity | Time required | What it tells us |
+|----------|--------------|------------------|
+| [activity] | [time] | [insight] |
+
+**Proposed check-in:** After [activity], regroup to decide whether to proceed 
+or pivot.
@@ -0,0 +1,63 @@
+---
+name: competitive-intelligence-monitor
+description: Continuously monitors competitor signals and surfaces strategic 
+implications for your roadmap. Use when user asks to "monitor competitors", 
+"track competitive landscape", "what are competitors doing this week", 
+"competitive briefing", or "what has changed in the market".
+metadata:
+  author: Mohit Aggarwal
+  version: 1.0.0
+  category: strategy
+  tags: [strategy, competitive-intel, roadmapping]
+  documentation: https://github.com/mohitagw15856/pm-claude-skills
+---
+# Competitive Intelligence Monitor Skill
+
+## Purpose
+Turn scattered competitor updates into structured weekly intelligence — not just 
+"what they did" but "what changed since last week and what it means for us."
+
+## Signal Categories to Monitor
+- **Product signals:** New features, removals, UX changes, beta programmes
+- **Pricing signals:** Changes to tiers, free limits, enterprise terms
+- **Hiring signals:** Job postings revealing strategic bets
+- **Partnership signals:** Integrations, acquisitions, ecosystem moves
+- **Messaging signals:** Changes in positioning, audience, value proposition
+
+## Process
+
+### First Run (Full Report)
+1. For each competitor provided, scan all five signal categories
+2. Categorise each signal found
+3. Assess: reactive (responding to market) or proactive (setting direction)?
+4. Rate threat level: High / Medium / Low / Watch
+5. Connect each signal to a specific item on the provided roadmap
+6. Recommend response: Accelerate / Deprioritise / Monitor / Investigate
+
+### Subsequent Runs (Diff Only)
+1. Compare current signals against previous run summary
+2. Output ONLY what is new or changed since last run
+3. Flag if a previously Low signal has escalated to High
+4. Keep output under 300 words — brevity is the point
+
+## Output Format
+
+### Competitive Intelligence Brief — [Date]
+**New Since Last Run:** [n signals]
+
+#### 🔴 High Priority
+**[Competitor]:** [Signal] → [Implication] → [Recommended action + owner]
+
+#### 🟡 Watch
+**[Competitor]:** [Signal] → [Why it matters now]
+
+#### ✅ No Change
+[Competitors with no new signals this week]
+
+**This Week's Strategic Summary:**
+[2 sentences max — what is the overall competitive landscape doing?]
+
+## OpenClaw Configuration
+Add to YAML frontmatter for scheduled runs:
+`schedule: weekly-monday-0800`
+Persistent memory stores last run summary for diff comparison.
@@ -0,0 +1,38 @@
+---
+name: competitor-signal-tracker
+description: Analyse competitor moves and surface strategic implications for your product
+tool_integration: Notion
+---
+# Competitor Signal Tracker Skill
+
+## Purpose
+Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
+
+## Signal Categories to Track
+- **Product signals:** New features, removals, UX changes, beta programmes
+- **Pricing signals:** Changes to tiers, free limits, enterprise terms
+- **Hiring signals:** Job postings that reveal strategic bets (e.g., hiring ML engineers = AI investment)
+- **Partnership signals:** Integrations, acquisitions, ecosystem moves
+- **Messaging signals:** Changes in positioning, target audience, value proposition
+
+## Process
+1. For each competitor update provided, categorise the signal type
+2. Assess: Is this reactive (responding to market) or proactive (setting direction)?
+3. Rate strategic threat level: High / Medium / Low / Watch
+4. Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
+5. Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
+
+## Output Format
+
+### Competitive Intelligence Report — [Date]
+
+#### [Competitor Name]
+**Signal:** [What they did]
+**Signal Type:** [Product / Pricing / Hiring / Partnership / Messaging]
+**Reactive or Proactive:** [assessment]
+**Threat Level:** [High / Medium / Low / Watch]
+**Implication for Us:** [Specific connection to our roadmap or strategy]
+**Recommended Response:** [Action + owner + timeline]
+
+#### Strategic Summary
+[2-3 sentences on the overall competitive landscape shift this week/month]
@@ -0,0 +1,44 @@
+---
+name: executive-update
+description: Transform detailed product updates into concise executive briefings
+tool_integration: Slack, Microsoft Teams
+---
+# Executive Update Skill
+
+## Purpose
+Produce a stakeholder update that busy executives will actually read — structured around what they care about: decisions, risks, and numbers.
+
+## Executive Communication Principles
+- Lead with the headline, not the context
+- Every update should answer: "So what does this mean for the business?"
+- Flag decisions needed clearly — don't bury asks in paragraphs
+- Be honest about risks — executives hate surprises more than bad news
+
+## Process
+1. Read the full product update provided
+2. Identify: key metric movements, decisions required, risks to flag, wins to celebrate
+3. Write in reverse pyramid style — most important first
+4. Limit to 250 words maximum for the main body
+5. Add a "Decisions Needed" section with clear options and your recommendation
+
+## Output Format
+
+### Product Update — [Date / Sprint / Month]
+**Headline:** [One sentence on the most important thing]
+
+**By the Numbers:**
+- [Metric 1]: [value] ([vs. target / last period])
+- [Metric 2]: [value] ([vs. target / last period])
+- [Metric 3]: [value] ([vs. target / last period])
+
+**Progress This Period:**
+[3-4 bullet points, outcome-focused not activity-focused]
+
+**Risks & Watch Items:**
+[2-3 bullets — be direct, include mitigation]
+
+**Decisions Needed:**
+1. [Decision] — Options: [A] or [B] — Recommendation: [your view] — Needed by: [date]
+
+**What's Next:**
+[2-3 bullets on next period priorities]
@@ -0,0 +1,61 @@
+---
+name: stakeholder-influence-mapper
+description: Maps stakeholders for a product decision and produces a tailored 
+influence strategy with draft talking points. Use when user needs to "get 
+alignment", "build consensus", "get buy-in from engineering or finance or legal", 
+"present to stakeholders", or "navigate organisational resistance".
+metadata:
+  author: Mohit Aggarwal
+  version: 1.0.0
+  category: stakeholder-communication
+  tags: [stakeholders, influence, communication, alignment]
+  documentation: https://github.com/mohitagw15856/pm-claude-skills
+---
+# Stakeholder Influence Mapper Skill
+
+## Purpose
+Turn a product initiative into a structured influence plan — who needs to be 
+aligned, in what order, and exactly what to say to each person in their language.
+
+## Required Inputs
+- Initiative description (what you want to do and why)
+- List of key stakeholders involved (name, role, relationship to initiative)
+- Timeline pressure (when do you need a decision?)
+- Any known objections or political context
+
+## Process
+1. Build stakeholder map with: role, primary concern, decision authority 
+   (blocker / influencer / informed), current stance (supportive / neutral / 
+   resistant / unknown)
+2. Identify the critical path of conversations — who must be won before others
+3. For each stakeholder, lead with their concern, not your ask
+4. Prepare one likely objection per stakeholder and a prepared response
+5. Flag any stakeholders who should NOT be approached until others are aligned
+
+## Output Format
+
+### Stakeholder Map: [Initiative Name]
+
+| Stakeholder | Role | Primary Concern | Authority | Current Stance |
+|-------------|------|-----------------|-----------|----------------|
+| [name] | [role] | [concern] | [type] | [stance] |
+
+### Recommended Conversation Sequence
+1. **[Name first]** — because [reason they unlock others]
+2. **[Name second]** — once [first] is aligned
+[continue...]
+
+### Talking Points by Stakeholder
+
+#### [Stakeholder Name]
+**Lead with:** [Their concern, not your feature]
+**Your ask:** [One specific thing you need from them]
+**Likely objection:** [What they'll push back on]
+**Prepared response:** [How to address it without being defensive]
+**What success looks like:** [What alignment from them looks like]
+
+## Notes
+- Never send the same message to all stakeholders — calibrate every time
+- Engineering leads want technical feasibility acknowledged first
+- Finance stakeholders want ROI framing before anything else
+- Legal/compliance stakeholders want risk mitigation addressed upfront
@@ -0,0 +1,71 @@
+---
+name: strategic-narrative-generator
+description: Generates the strategic story connecting your roadmap to company 
+goals in a form non-technical stakeholders can repeat. Use when user needs to 
+"explain the roadmap", "present strategy to leadership or the board", "write the 
+why behind the roadmap", "create a narrative for all-hands", or "make the 
+roadmap tell a story".
+metadata:
+  author: Mohit Aggarwal
+  version: 1.0.0
+  category: roadmapping
+  tags: [strategy, roadmap, executive-communication, narrative]
+  documentation: https://github.com/mohitagw15856/pm-claude-skills
+---
+# Strategic Narrative Generator Skill
+
+## Purpose
+Turn a prioritised initiative list into a strategic narrative — the story that 
+explains not just what you're building but why, why now, and why this sequence. 
+The kind of narrative a board member can repeat back correctly after one hearing.
+
+## Required Inputs
+- Prioritised initiative list (with rough timelines)
+- Current OKRs or strategic priorities (1-3)
+- Competitive or market context (optional but improves output significantly)
+
+## Process
+1. Read the initiative list and identify 2-3 natural strategic themes
+2. For each theme: articulate the problem it addresses, the customer it serves, 
+   and the metric it moves
+3. Build the progression narrative: how does Q1 set up Q2? How does H1 set up H2?
+4. Write executive summary in under 100 words (the version someone can repeat)
+5. Anticipate the 3 hardest questions a sceptical board member would ask — 
+   and draft answers
+6. Identify what's NOT on the roadmap and why (this builds credibility)
+
+## Output Format
+
+### Product Strategy Narrative: [Period]
+
+**The One-Paragraph Context:**
+[Market moment + key challenge + our response — for the CFO, not the engineer]
+
+**Strategic Theme 1: [Name]**
+- The problem: [customer pain in plain language]
+- Our response: [initiatives in this theme]
+- The metric it moves: [specific and measurable]
+- Why now: [timing rationale]
+
+**Strategic Theme 2: [Name]**
+[Same structure]
+
+**The Progression Story:**
+[How each quarter sets up the next — this is the narrative arc]
+
+**Executive Summary (under 100 words — shareable):**
+[Version someone can quote at a board meeting]
+
+**Questions to Prepare For:**
+1. [Hard question] → [Prepared answer]
+2. [Hard question] → [Prepared answer]
+3. [Hard question] → [Prepared answer]
+
+**What's Not on the Roadmap (and Why):**
+[2-3 items — shows strategic discipline, not just prioritisation]
+
+## Tone Rules
+- Write for a CFO, not an engineer
+- Lead with outcomes, not features
+- Every sentence should answer "so what?"
+- Avoid jargon — if you can't say it plainly, the strategy isn't clear enough yet
@@ -0,0 +1,157 @@
+#!/bin/bash
+# Run this from your repo root: cd pm-claude-skills && bash setup-marketplace.sh
+# This creates the full plugin structure and copies all SKILL.md files into place.
+
+echo "=== Creating plugin bundle directories ==="
+
+# ─────────────────────────────────────────
+# BUNDLE 1: pm-essentials (5 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-essentials/.claude-plugin
+mkdir -p plugins/pm-essentials/skills/prd-template
+mkdir -p plugins/pm-essentials/skills/meeting-notes
+mkdir -p plugins/pm-essentials/skills/stakeholder-update
+mkdir -p plugins/pm-essentials/skills/user-research-synthesis
+mkdir -p plugins/pm-essentials/skills/competitive-analysis
+
+cp skills/prd-template/SKILL.md              plugins/pm-essentials/skills/prd-template/SKILL.md
+cp skills/meeting-notes/SKILL.md             plugins/pm-essentials/skills/meeting-notes/SKILL.md
+cp skills/stakeholder-update/SKILL.md        plugins/pm-essentials/skills/stakeholder-update/SKILL.md
+cp skills/user-research-synthesis/SKILL.md   plugins/pm-essentials/skills/user-research-synthesis/SKILL.md
+cp skills/competitive-analysis/SKILL.md      plugins/pm-essentials/skills/competitive-analysis/SKILL.md
+
+echo "✓ pm-essentials done (5 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 2: pm-discovery (4 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-discovery/.claude-plugin
+mkdir -p plugins/pm-discovery/skills/discovery-interview-guide
+mkdir -p plugins/pm-discovery/skills/job-story-mapper
+mkdir -p plugins/pm-discovery/skills/user-interview-synthesis
+mkdir -p plugins/pm-discovery/skills/assumption-mapper
+
+cp skills/discovery-interview-guide/SKILL.md plugins/pm-discovery/skills/discovery-interview-guide/SKILL.md
+cp skills/job-story-mapper/SKILL.md           plugins/pm-discovery/skills/job-story-mapper/SKILL.md
+cp skills/user-interview-synthesis/SKILL.md   plugins/pm-discovery/skills/user-interview-synthesis/SKILL.md
+cp skills/assumption-mapper/SKILL.md          plugins/pm-discovery/skills/assumption-mapper/SKILL.md
+
+echo "✓ pm-discovery done (4 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 3: pm-planning (7 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-planning/.claude-plugin
+mkdir -p plugins/pm-planning/skills/okr-builder
+mkdir -p plugins/pm-planning/skills/feature-prioritisation
+mkdir -p plugins/pm-planning/skills/roadmap-presentation
+mkdir -p plugins/pm-planning/skills/pricing-strategy
+mkdir -p plugins/pm-planning/skills/rice-prioritisation
+mkdir -p plugins/pm-planning/skills/roadmap-narrative
+mkdir -p plugins/pm-planning/skills/rice-impact-matrix
+
+cp skills/okr-builder/SKILL.md               plugins/pm-planning/skills/okr-builder/SKILL.md
+cp skills/feature-prioritisation/SKILL.md    plugins/pm-planning/skills/feature-prioritisation/SKILL.md
+cp skills/roadmap-presentation/SKILL.md      plugins/pm-planning/skills/roadmap-presentation/SKILL.md
+cp skills/pricing-strategy/SKILL.md          plugins/pm-planning/skills/pricing-strategy/SKILL.md
+cp skills/rice-prioritisation/SKILL.md       plugins/pm-planning/skills/rice-prioritisation/SKILL.md
+cp skills/roadmap-narrative/SKILL.md         plugins/pm-planning/skills/roadmap-narrative/SKILL.md
+cp skills/rice-impact-matrix/SKILL.md        plugins/pm-planning/skills/rice-impact-matrix/SKILL.md
+
+echo "✓ pm-planning done (7 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 4: pm-delivery (7 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-delivery/.claude-plugin
+mkdir -p plugins/pm-delivery/skills/sprint-planning
+mkdir -p plugins/pm-delivery/skills/technical-spec-template
+mkdir -p plugins/pm-delivery/skills/ab-test-planner
+mkdir -p plugins/pm-delivery/skills/go-to-market-planner
+mkdir -p plugins/pm-delivery/skills/product-launch-checklist
+mkdir -p plugins/pm-delivery/skills/sprint-brief
+mkdir -p plugins/pm-delivery/skills/retro-analysis
+
+cp skills/sprint-planning/SKILL.md           plugins/pm-delivery/skills/sprint-planning/SKILL.md
+cp skills/technical-spec-template/SKILL.md   plugins/pm-delivery/skills/technical-spec-template/SKILL.md
+cp skills/ab-test-planner/SKILL.md           plugins/pm-delivery/skills/ab-test-planner/SKILL.md
+cp skills/go-to-market-planner/SKILL.md      plugins/pm-delivery/skills/go-to-market-planner/SKILL.md
+cp skills/product-launch-checklist/SKILL.md  plugins/pm-delivery/skills/product-launch-checklist/SKILL.md
+cp skills/sprint-brief/SKILL.md              plugins/pm-delivery/skills/sprint-brief/SKILL.md
+cp skills/retro-analysis/SKILL.md            plugins/pm-delivery/skills/retro-analysis/SKILL.md
+
+echo "✓ pm-delivery done (7 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 5: pm-analytics (3 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-analytics/.claude-plugin
+mkdir -p plugins/pm-analytics/skills/data-analysis-standard
+mkdir -p plugins/pm-analytics/skills/retention-analysis
+mkdir -p plugins/pm-analytics/skills/product-health-analysis
+
+cp skills/data-analysis-standard/SKILL.md   plugins/pm-analytics/skills/data-analysis-standard/SKILL.md
+cp skills/retention-analysis/SKILL.md       plugins/pm-analytics/skills/retention-analysis/SKILL.md
+cp skills/product-health-analysis/SKILL.md  plugins/pm-analytics/skills/product-health-analysis/SKILL.md
+
+echo "✓ pm-analytics done (3 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 6: pm-strategy (6 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-strategy/.claude-plugin
+mkdir -p plugins/pm-strategy/skills/competitor-signal-tracker
+mkdir -p plugins/pm-strategy/skills/competitive-intelligence-monitor
+mkdir -p plugins/pm-strategy/skills/stakeholder-influence-mapper
+mkdir -p plugins/pm-strategy/skills/strategic-narrative-generator
+mkdir -p plugins/pm-strategy/skills/executive-update
+mkdir -p plugins/pm-strategy/skills/ambiguity-resolver
+
+cp skills/competitor-signal-tracker/SKILL.md          plugins/pm-strategy/skills/competitor-signal-tracker/SKILL.md
+cp skills/competitive-intelligence-monitor/SKILL.md   plugins/pm-strategy/skills/competitive-intelligence-monitor/SKILL.md
+cp skills/stakeholder-influence-mapper/SKILL.md       plugins/pm-strategy/skills/stakeholder-influence-mapper/SKILL.md
+cp skills/strategic-narrative-generator/SKILL.md      plugins/pm-strategy/skills/strategic-narrative-generator/SKILL.md
+cp skills/executive-update/SKILL.md                   plugins/pm-strategy/skills/executive-update/SKILL.md
+cp skills/ambiguity-resolver/SKILL.md                 plugins/pm-strategy/skills/ambiguity-resolver/SKILL.md
+
+echo "✓ pm-strategy done (6 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 7: pm-advanced (4 skills)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-advanced/.claude-plugin
+mkdir -p plugins/pm-advanced/skills/ai-product-canvas
+mkdir -p plugins/pm-advanced/skills/multi-source-signal-synthesiser
+mkdir -p plugins/pm-advanced/skills/experiment-designer
+mkdir -p plugins/pm-advanced/skills/design-handoff-brief
+
+cp skills/ai-product-canvas/SKILL.md                 plugins/pm-advanced/skills/ai-product-canvas/SKILL.md
+cp skills/multi-source-signal-synthesiser/SKILL.md   plugins/pm-advanced/skills/multi-source-signal-synthesiser/SKILL.md
+cp skills/experiment-designer/SKILL.md               plugins/pm-advanced/skills/experiment-designer/SKILL.md
+cp skills/design-handoff-brief/SKILL.md              plugins/pm-advanced/skills/design-handoff-brief/SKILL.md
+
+echo "✓ pm-advanced done (4 skills)"
+
+# ─────────────────────────────────────────
+# BUNDLE 8: pm-rituals (1 skill)
+# ─────────────────────────────────────────
+mkdir -p plugins/pm-rituals/.claude-plugin
+mkdir -p plugins/pm-rituals/skills/pm-weekly-review
+
+cp skills/pm-weekly-review/SKILL.md  plugins/pm-rituals/skills/pm-weekly-review/SKILL.md
+
+echo "✓ pm-rituals done (1 skill)"
+
+# ─────────────────────────────────────────
+# SUMMARY
+# ─────────────────────────────────────────
+echo ""
+echo "=== All done! 33 skills across 8 plugin bundles ==="
+echo ""
+echo "Next steps:"
+echo "  1. Copy marketplace.json   → .claude-plugin/marketplace.json"
+echo "  2. Copy plugin.json        → plugins/<bundle>/.claude-plugin/plugin.json  (for each bundle)"
+echo "  3. git add . && git commit -m 'add marketplace plugin structure' && git push"
+echo "  4. Test in Claude Code:"
+echo "     /plugin marketplace add mohitagw15856/pm-claude-skills"
+echo "     /plugin install pm-essentials@pm-claude-skills"
@@ -0,0 +1,95 @@
+---
+name: ab-test-planner
+description: Designs statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, run an A/B test, calculate sample size, or interpret test results. Triggers on "A/B test", "experiment", "split test", "statistical significance", "sample size".
+---
+
+# A/B Test Planner Skill
+
+Design experiments that produce trustworthy results — not just directional signals. Every test output includes hypothesis, success metrics, sample size, duration, and a results interpretation guide.
+
+## Experiment Design Checklist
+
+Before running any test, confirm:
+- [ ] Clear hypothesis with predicted direction
+- [ ] Single primary metric (plus up to 2 guardrail metrics)
+- [ ] Minimum detectable effect (MDE) defined
+- [ ] Sample size calculated
+- [ ] Test duration estimated
+- [ ] Segment isolated (no overlap with other running tests)
+- [ ] Rollback plan defined
+
+## Hypothesis Template
+
+> "We believe that [change] will cause [primary metric] to [increase/decrease] by [X%] for [user segment], because [rationale based on data or insight]."
+
+Never run a test without a directional hypothesis. "Let's just see what happens" is not a hypothesis.
+
+## Sample Size Calculator Logic
+
+Use this formula (provide the output, not the formula, to the user):
+
+- **Baseline conversion rate:** Current rate of primary metric
+- **MDE:** Smallest change worth detecting (recommend 10–20% relative lift for most features)
+- **Statistical power:** 80% (standard)
+- **Significance level:** 95% (p < 0.05)
+
+For common scenarios, provide pre-calculated estimates:
+
+| Baseline Rate | MDE (Relative) | Required Sample per Variant |
+|---|---|---|
+| 5% | 20% | ~19,000 |
+| 10% | 15% | ~14,000 |
+| 20% | 10% | ~15,000 |
+| 40% | 10% | ~9,500 |
+| 60% | 5% | ~42,000 |
+
+Always warn: "These are estimates. Use a tool like Evan Miller's calculator or Statsig for precision."
+
+## Test Duration Guidance
+
+Minimum: 2 full weeks (to capture weekly seasonality)
+Maximum: 4 weeks (novelty effect distorts results beyond this)
+
+`Duration = Required sample ÷ (Daily traffic × % exposed)`
+
+Flag if traffic is too low to reach significance in under 8 weeks — recommend a different approach (e.g., holdout test, qualitative research).
+
+## Output Format
+
+### A/B Test Plan — [Test Name] — [Date]
+
+**Hypothesis:**
+> [Filled hypothesis template]
+
+**Variants:**
+- Control (A): [Current experience]
+- Treatment (B): [Changed experience — be specific]
+
+**Primary Metric:** [Metric name + how measured]
+**Guardrail Metrics:** [Metrics that must not degrade]
+
+**Target Segment:** [Who sees the test — % of traffic, user type]
+**Traffic Split:** [50/50 recommended unless ramp-up needed]
+
+**Sample Size Required:** ~[N] users per variant
+**Estimated Duration:** [X] weeks (based on [Y] daily eligible users)
+**Significance Threshold:** 95% confidence, 80% power
+
+**Exclusions:** [Any user segments to exclude and why]
+
+**Rollback Trigger:** If [guardrail metric] degrades by [X%], stop the test immediately.
+
+**Results Interpretation Guide:**
+- ✅ Ship if: Treatment shows [X%]+ lift on primary metric at 95% confidence AND guardrail metrics are stable
+- 🔄 Iterate if: Direction is positive but not significant — consider extending or redesigning
+- ❌ Reject if: No lift or negative direction at significance
+- ⚠️ Inconclusive: Do not ship. Do not call it a win.
+
+---
+
+## Guidelines
+
+- Always recommend against peeking at results before the test reaches planned sample size — explain p-hacking risk
+- If user wants to test multiple variants, explain the multiple comparisons problem and recommend a Bonferroni correction or a Bayesian approach
+- If traffic is very low (<1,000 users/day), recommend qualitative alternatives: moderated testing, 5-second tests, or user interviews
+- Never approve a test with no guardrail metrics — always protect revenue, retention, or core engagement
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
mohitagw15856	e612ba45b1	fix: update marketplace.json to v4.0.0 with 14 plugins	2026-04-02 09:54:42 +01:00
mohitagw15856	fb235be09a	feat: add 6 new plugin bundles (pm-gtm, pm-engineering, pm-data, pm-people, pm-design, pm-business)	2026-04-02 09:35:59 +01:00
mohitagw15856	f9b79a48b9	add folders in plugins	2026-04-02 09:19:07 +01:00
mohitagw15856	7ad6ec62fa	merge remote changes	2026-04-02 09:04:17 +01:00
mohitagw15856	c3efe0cdef	feat: add go-to-market	2026-04-02 09:01:04 +01:00
mohitagw15856	e501288bfc	Update QUICKSTART.md	2026-04-02 13:24:30 +05:30
mohitagw15856	093d0e0061	Update CONTRIBUTING.md	2026-04-02 13:24:08 +05:30
mohitagw15856	e49327205f	Update README.md	2026-04-02 13:23:23 +05:30
mohitagw15856	6af3f21689	feat: add 20 new skills across 6 professions (skills 34-53) + open source contributing guide	2026-04-02 08:51:21 +01:00
mohitagw15856	22c9e33861	Update README.md	2026-03-26 13:24:47 +05:30
mohitagw15856	8ac9266aec	Update README.md	2026-03-23 17:06:47 +05:30
mohitagw15856	05a4af1c27	Update README.md	2026-03-23 17:03:04 +05:30
mohitagw15856	e9e9f08c96	Update README.md	2026-03-23 17:02:29 +05:30
mohitagw15856	d1b06591cb	add plugin.json manifests for all 8 PM skill bundles	2026-03-23 08:22:21 +00:00
mohitagw15856	6113761ecb	add marketplace plugin structure	2026-03-23 08:13:37 +00:00
mohitagw15856	6b42687fde	Create marketplace.json	2026-03-23 13:38:30 +05:30
mohitagw15856	4f14c7cd7c	Update README.md	2026-03-23 01:47:53 +05:30
mohitagw15856	96109f1cdd	move skills into skills/ directory	2026-03-22 20:07:15 +00:00
mohitagw15856	cbd22b57a6	New 15 more skills	2026-03-23 01:21:43 +05:30
mohitagw15856	994bf95eba	Merge pull request #2 from mohitagw15856/Advanced-Skills Advanced skills	2026-02-22 18:45:11 +00:00
mohitagw15856	4accc3407c	Update README.md	2026-02-22 18:44:30 +00:00
mohitagw15856	4e66c45520	Create SKILL.md New Skill: strategic-narrative-generator	2026-02-22 18:41:10 +00:00
mohitagw15856	6947f16685	Create SKILL.md New Skill: multi-source-signal-synthesiser	2026-02-22 18:40:47 +00:00
mohitagw15856	c08080a60a	Create SKILL.md New Skill: ambiguity-resolver	2026-02-22 18:40:23 +00:00
mohitagw15856	6617faa3ac	Create SKILL.md New Skill: stakeholder-influence-mapper	2026-02-22 18:39:57 +00:00
mohitagw15856	0b53f2caa3	Create SKILL.md New skill: experiment-designer	2026-02-22 18:39:28 +00:00
mohitagw15856	be0349866a	Create SKILL.md New skill: Competitive intelligence monitor	2026-02-22 18:38:25 +00:00
mohitagw15856	06aae11156	Create FUNDING.yml	2026-02-20 12:15:54 +00:00