Update README.md

Advanced skills

.claude-plugin/marketplace.json

@@ -0,0 +1,180 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "pm-claude-skills",
+  "version": "5.0.0",
+  "description": "80 Claude Skills across 13 professions — product management, marketing, engineering, data, design, leadership, legal, finance, HR, sales, operations, research, and more. 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"
+    },
+    {
+      "name": "pm-legal",
+      "description": "Legal skills: Contract Review, NDA Analyser, Legal Brief, Compliance Checklist. Flag risks in contracts and NDAs, draft legal memos in IRAC format, and generate GDPR, SOC 2, FCA and other compliance checklists. Not a substitute for qualified legal advice.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-legal",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-finance",
+      "description": "Finance skills: Financial Model Narrative, Budget Variance Analysis, Investor Pitch Deck, Financial Due Diligence. Turn numbers into board-ready narratives, explain variances, structure pitch decks, and generate DD checklists.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-finance",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-hr",
+      "description": "HR skills: Job Description Writer, Onboarding Plan, Employee Engagement Survey, Redundancy Consultation. Write inclusive JDs, build 30/60/90-day plans, design engagement surveys, and structure legally compliant redundancy processes.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-hr",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-sales",
+      "description": "Sales skills: Sales Battlecard, Discovery Call Prep, Proposal Writer, Account Plan. Build competitive battlecards, prepare structured discovery calls, write winning proposals, and create strategic account plans.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-sales",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-operations",
+      "description": "Operations skills: Process Documentation, SOP Writer, Vendor Evaluation, Project Status Report. Document workflows, write audit-ready SOPs, evaluate vendors with weighted scorecards, and produce RAG status reports.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-operations",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-research",
+      "description": "Research and healthcare skills: Clinical Case Summary, Research Protocol, Patient Communication, Literature Review. Write SBAR handovers, design research protocols, draft accessible patient communications, and structure literature reviews.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-research",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    },
+    {
+      "name": "pm-cross",
+      "description": "Cross-profession skills: Press Release, Grant Proposal, Executive Summary. Write journalist-ready press releases, structure grant applications aligned to funder priorities, and produce decision-ready executive summaries for any audience.",
+      "version": "1.0.0",
+      "category": "productivity",
+      "source": "./plugins/pm-cross",
+      "homepage": "https://github.com/mohitagw15856/pm-claude-skills"
+    }
+  ]
+}

.github/FUNDING.yml

@@ -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']

CODE_OF_CONDUCT.md

@@ -0,0 +1,39 @@
+# Code of Conduct
+
+## Our Pledge
+
+This is an open-source community built around sharing useful Claude Skills across professions. Everyone who contributes, raises issues, or participates in discussions is expected to make this a welcoming and constructive space.
+
+We pledge to make participation in this project a harassment-free experience for everyone, regardless of age, background, disability, ethnicity, gender identity, level of experience, nationality, personal appearance, race, religion, or sexual identity.
+
+## Our Standards
+
+**Behaviour that helps this community thrive:**
+- Sharing skills that solve real workflows, with honest descriptions of what they do
+- Giving constructive feedback on PRs — specific, actionable, and respectful
+- Acknowledging other contributors' work
+- Being direct about limitations or gaps in a skill without being dismissive
+- Helping newcomers get their first PR merged
+
+**Behaviour that is not acceptable:**
+- Harassment, personal attacks, or dismissive comments on contributions
+- Submitting skills that contain malicious instructions or prompt injection attempts
+- Spamming issues or PRs with low-effort or off-topic content
+- Claiming credit for someone else's skill file
+- Any form of discrimination
+
+## Scope
+
+This Code of Conduct applies to all spaces managed by this project — GitHub Issues, Pull Requests, Discussions, and any other forums linked from this repo.
+
+## Reporting
+
+If you experience or witness unacceptable behaviour, contact the maintainer directly at **mohit15856@gmail.com**. All reports will be reviewed and responded to promptly and confidentially.
+
+## Enforcement
+
+The maintainer reserves the right to remove comments, close PRs, or ban contributors who violate this Code of Conduct. Decisions will be made fairly and explained where possible.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.

CONTRIBUTING.md

@@ -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.*

QUICKSTART.md

@@ -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.
 

README.md

@@ -1,247 +1,330 @@
-# Product Management Claude Skills
+# 🧠 Claude Skills Library — 80 Skills for Every Profession
 
-**Transform your PM workflow with specialized Claude Skills for common product management tasks.**
+> **Save 8–10 hours per week across 13 professions. 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, legal, finance, HR, sales, operations, research, and more. 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 https://github.com/mohitagw15856/pm-claude-skills
+
+
+Or install by profession:
+
+claude plugin install pm-essentials@pm-claude-skills     # Core PM
+claude plugin install pm-legal@pm-claude-skills          # Legal
+claude plugin install pm-finance@pm-claude-skills        # Finance
+claude plugin install pm-hr@pm-claude-skills             # HR
+claude plugin install pm-sales@pm-claude-skills          # Sales
+claude plugin install pm-operations@pm-claude-skills     # Operations
+claude plugin install pm-research@pm-claude-skills       # Research & Healthcare
+claude plugin install pm-cross@pm-claude-skills          # Cross-profession
+
+
+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/
+
+
+---
+
+## 📚 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 | [Read →](https://medium.com/product-powerhouse/i-built-20-new-claude-skills-for-every-profession-heres-the-full-library-50278e00bf72)|
+| Part 9 | 80 Claude Skills for Every Profession — Lawyers, Doctors, Finance, HR, Sales and More | *Latest — Link TBC* |
+
+---
+
+## 🗂️ All 80 Skills
+
+### 🛠️ Product Management (Skills 1–33)
+**Bundles:** `pm-essentials` · `pm-discovery` · `pm-planning` · `pm-delivery` · `pm-analytics` · `pm-strategy` · `pm-advanced` · `pm-rituals`
+
+> The original toolkit covering the full PM lifecycle — discovery, prioritisation, delivery, strategy, stakeholder comms, and weekly rituals.
+
+| # | Skill | What It Does |
+|---|---|---|
+| 1–5 | **pm-essentials** | PRD Template, Meeting Notes, Stakeholder Update, User Research Synthesis, Competitive Analysis |
+| 6–9 | **pm-discovery** | Discovery Interview Guide, Job Story Mapper, User Interview Synthesis, Assumption Mapper |
+| 10–15 | **pm-planning** | OKR Builder, Feature Prioritisation (RICE/MoSCoW/Kano/ICE), Roadmap Presentation, Pricing Strategy |
+| 16–22 | **pm-delivery** | Sprint Planning, Technical Spec, A/B Test Planner, Go-to-Market Planner, Launch Checklist, Sprint Brief, Retro |
+| 23–25 | **pm-analytics** | Data Analysis Standard, Retention Analysis, Product Health Analysis |
+| 26–31 | **pm-strategy** | Competitor Signal Tracker, Competitive Intelligence Monitor, Stakeholder Influence Mapper, Strategic Narrative, Executive Update, Ambiguity Resolver |
+| 32–33 | **pm-advanced** | AI Product Canvas, Multi-Source Signal Synthesiser, Experiment Designer, Design Handoff Brief |
+
+> 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 PM skills detail.
+
+---
+
+### 📣 Marketing & GTM (Skills 34–37)
+**Bundle:** `pm-gtm`
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 34 | **Go-To-Market** | `skills/go-to-market/` | Positioning statements, messaging pillars, feature/benefit mapping, role-specific use cases |
+| 35 | **Content Calendar** | `skills/content-calendar/` | Multi-channel content calendars with opening 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)
+**Bundle:** `pm-engineering`
+
+| # | 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: endpoints, parameters, response schemas, code examples |
+| 41 | **Architecture Decision Record** | `skills/architecture-decision-record/` | ADRs with context, options considered, decision, consequences, and risks |
+
+---
+
+### 📊 Data & Analytics (Skills 42–44)
+**Bundle:** `pm-data`
+
+| # | 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 & People (Skills 45–47)
+**Bundle:** `pm-people`
+
+| # | 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)
+**Bundle:** `pm-design`
+
+| # | 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)
+**Bundle:** `pm-business`
+
+| # | 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 |
+
+---
+
+### ⚖️ Legal (Skills 54–57)
+**Bundle:** `pm-legal`
+
+> ⚠️ All legal skills include a disclaimer. Not a substitute for qualified legal advice.
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 54 | **Contract Review** | `skills/contract-review/` | Structured review with key terms, flagged clauses, risk rating, and plain English summary |
+| 55 | **NDA Analyser** | `skills/nda-analyser/` | Clause-by-clause NDA analysis with risk flags and negotiation checklist |
+| 56 | **Legal Brief** | `skills/legal-brief/` | Legal memos and argument outlines in IRAC format (Issue, Rule, Application, Conclusion) |
+| 57 | **Compliance Checklist** | `skills/compliance-checklist/` | GDPR, SOC 2, ISO 27001, FCA, HIPAA compliance checklists with prioritised gap analysis |
+
+---
+
+### 💰 Finance (Skills 58–61)
+**Bundle:** `pm-finance`
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 58 | **Financial Model Narrative** | `skills/financial-model-narrative/` | Turns P&L and model outputs into board-ready written narratives |
+| 59 | **Budget Variance Analysis** | `skills/budget-variance-analysis/` | Variance table with root cause commentary and management summary |
+| 60 | **Investor Pitch Deck** | `skills/investor-pitch-deck/` | Slide-by-slide pitch deck structure with what each slide must prove |
+| 61 | **Financial Due Diligence** | `skills/financial-due-diligence/` | DD document request list, analytical questions, and red flags checklist |
+
+---
+
+### 👥 HR (Skills 62–65)
+**Bundle:** `pm-hr`
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 62 | **Job Description Writer** | `skills/job-description-writer/` | Inclusive, structured JDs with built-in language review and salary range nudge |
+| 63 | **Onboarding Plan** | `skills/onboarding-plan/` | 30/60/90-day plans with week-by-week structure, milestones, and manager checklist |
+| 64 | **Employee Engagement Survey** | `skills/employee-engagement-survey/` | Survey design + results analysis mode with eNPS and action planning template |
+| 65 | **Redundancy Consultation** | `skills/redundancy-consultation/` | Process timeline, at-risk letter, consultation script, and confirmation letter — UK law |
+
+---
+
+### 🤝 Sales (Skills 66–69)
+**Bundle:** `pm-sales`
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 66 | **Sales Battlecard** | `skills/sales-battlecard/` | One-page competitive battlecard with objection responses and landmine questions |
+| 67 | **Discovery Call Prep** | `skills/discovery-call-prep/` | Call brief with research summary, hypothesis, structured questions, and success criteria |
+| 68 | **Proposal Writer** | `skills/proposal-writer/` | Commercial proposals structured around the prospect's problem, not the product |
+| 69 | **Account Plan** | `skills/account-plan/` | Strategic account plan with relationship map, whitespace analysis, risks, and 90-day actions |
+
+---
+
+### ⚙️ Operations (Skills 70–73)
+**Bundle:** `pm-operations`
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 70 | **Process Documentation** | `skills/process-documentation/` | Clear process docs with steps, roles, edge cases — followable by a new starter |
+| 71 | **SOP Writer** | `skills/sop-writer/` | Formal, audit-ready SOPs with version control, quality checks, and non-conformance process |
+| 72 | **Vendor Evaluation** | `skills/vendor-evaluation/` | Weighted vendor scorecard, RFP questions, reference check template, and recommendation |
+| 73 | **Project Status Report** | `skills/project-status-report/` | RAG status reports with milestone progress, issues, risks, and decisions required |
+
+---
+
+### 🏥 Research & Healthcare (Skills 74–77)
+**Bundle:** `pm-research`
+
+> ⚠️ Healthcare skills are for documentation and educational purposes only. All clinical content must be reviewed by a qualified professional.
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 74 | **Clinical Case Summary** | `skills/clinical-case-summary/` | SBAR handovers, SOAP notes, and case reports for educational and documentation use |
+| 75 | **Research Protocol** | `skills/research-protocol/` | Complete study protocols with objectives, methodology, ethics, and analysis plan |
+| 76 | **Patient Communication** | `skills/patient-communication/` | Plain English patient letters, leaflets, and results communications at Grade 6 reading level |
+| 77 | **Literature Review** | `skills/literature-review/` | Thematically organised literature reviews with synthesis, critical analysis, and gap identification |
+
+---
+
+### 🌐 Cross-Profession (Skills 78–80)
+**Bundle:** `pm-cross`
+
+| # | Skill | Folder | What It Does |
+|---|---|---|---|
+| 78 | **Press Release** | `skills/press-release/` | Journalist-ready press releases with headline rules, boilerplate, and journalist test |
+| 79 | **Grant Proposal** | `skills/grant-proposal/` | Complete grant applications aligned to funder priorities with budget narrative |
+| 80 | **Executive Summary** | `skills/executive-summary/` | Decision-ready executive summaries with bottom line upfront, adapted for any audience |
+
+---
+
+## 🤝 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. Use when [trigger condition]. Produces [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):
+
+| Skill | Profession | Use Case |
+|---|---|---|
+| `teaching-lesson-plan` | Education | Structured lesson plans from curriculum objectives |
+| `seo-content-brief` | Marketing | Content briefs with keyword strategy and outline |
+| `grant-report` | Non-profit | Funder progress reports against grant objectives |
+| `architectural-spec` | Architecture | Project specifications and technical drawing briefs |
+| `media-pitch` | Journalism | Story pitches to editors and commissioning briefs |
+| `clinical-guideline-summary` | Healthcare | Plain English summaries of clinical guidelines |
+| `tax-planning-checklist` | Finance | Year-end tax planning checklist by entity type |
+| `sales-forecasting-model` | Sales | Structured pipeline forecasting and commentary |
+
+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. 🙌
+
+---
+
+## 📦 All Plugin Bundles
+
+Install the whole library or just the bundles you need:
+
+# Install everything
+/plugin marketplace add https://github.com/mohitagw15856/pm-claude-skills
+
+# Install by profession
+claude plugin install pm-essentials@pm-claude-skills
+claude plugin install pm-discovery@pm-claude-skills
+claude plugin install pm-planning@pm-claude-skills
+claude plugin install pm-delivery@pm-claude-skills
+claude plugin install pm-analytics@pm-claude-skills
+claude plugin install pm-strategy@pm-claude-skills
+claude plugin install pm-advanced@pm-claude-skills
+claude plugin install pm-rituals@pm-claude-skills
+claude plugin install pm-gtm@pm-claude-skills
+claude plugin install pm-engineering@pm-claude-skills
+claude plugin install pm-data@pm-claude-skills
+claude plugin install pm-people@pm-claude-skills
+claude plugin install pm-design@pm-claude-skills
+claude plugin install pm-business@pm-claude-skills
+claude plugin install pm-legal@pm-claude-skills
+claude plugin install pm-finance@pm-claude-skills
+claude plugin install pm-hr@pm-claude-skills
+claude plugin install pm-sales@pm-claude-skills
+claude plugin install pm-operations@pm-claude-skills
+claude plugin install pm-research@pm-claude-skills
+claude plugin install pm-cross@pm-claude-skills
+
+
+---
+
+## 📖 How Skills Work
+
+Skills are markdown files that Claude reads dynamically. When you describe a task, Claude scans available skill descriptions (~100 tokens) and loads the full skill only when 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
+- Plugin skills install via the Claude Code marketplace with one command
+
+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 — raise a PR, open a discussion, or tag me in your article.
+
+---
+
+*Built and maintained by [Mohit Aggarwal](https://medium.com/@mohit15856) | [Product Notes publication](https://medium.com/product-powerhouse)*

SECURITY.md

@@ -0,0 +1,55 @@
+# Security Policy
+
+## Overview
+
+This repository contains Claude Skill files — plain markdown instruction files that teach Claude how to perform professional tasks. There are no backend services, APIs, authentication systems, or databases in this repo.
+
+That said, security matters here in two specific ways: **skill file safety** and **prompt injection risks**.
+
+## Supported Versions
+
+| Version | Supported |
+|---|---|
+| v4.0.0 (latest) | ✅ Active |
+| v3.0.0 | ✅ Security fixes only |
+| < v3.0.0 | ❌ No longer supported |
+
+## Skill File Safety
+
+All skills in this repo are reviewed before merging to ensure they:
+
+- Do not contain instructions designed to manipulate Claude into ignoring its guidelines
+- Do not attempt prompt injection (e.g. hidden instructions to override system behaviour)
+- Do not instruct Claude to request, store, or transmit personal or sensitive data
+- Do not contain malicious commands disguised as skill instructions
+- Do not include hardcoded credentials, API keys, or personally identifiable information
+
+**If you are installing skills from this repo:** skills are plain text markdown files. They do not execute code, make network requests, or access your file system on their own. Review any skill file before installing if you have concerns.
+
+## Reporting a Vulnerability
+
+If you discover a skill file in this repo that contains malicious instructions, a prompt injection attempt, or any content that could cause harm to users of Claude Code, please report it **privately** before raising a public issue.
+
+**How to report:**
+
+Email: **mohit15856@gmail.com**
+Subject line: `[SECURITY] pm-claude-skills — <brief description>`
+
+Include:
+- The skill file path (e.g. `plugins/pm-gtm/skills/go-to-market/SKILL.md`)
+- A description of the issue
+- Why you believe it is a security concern
+
+**Response time:** You will receive an acknowledgement within 48 hours and a resolution or update within 7 days.
+
+Please do not open a public GitHub Issue for security vulnerabilities — use the email above. Public disclosure before a fix is in place puts other users at risk.
+
+## Community Contributions
+
+All pull requests adding new skill files are reviewed for the safety criteria listed above before merging. If you are submitting a skill, ensure it:
+
+- Only contains instructions relevant to the stated professional workflow
+- Does not include any attempt to override Claude's built-in guidelines
+- Does not ask Claude to collect or relay user data
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for full contribution guidelines.

add-plugin-json.sh

@@ -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 ==="

create-plugin-jsons.sh

@@ -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 "================================================"

plugins/create-plugin-jsons.sh

@@ -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 "================================================"

plugins/pm-advanced/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-advanced/skills/ai-product-canvas/SKILL.md

@@ -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

plugins/pm-advanced/skills/design-handoff-brief/SKILL.md

@@ -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]

plugins/pm-advanced/skills/experiment-designer/SKILL.md

@@ -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

plugins/pm-advanced/skills/multi-source-signal-synthesiser/SKILL.md

@@ -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.

plugins/pm-analytics/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-analytics/skills/data-analysis-standard/SKILL.md

@@ -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"

plugins/pm-analytics/skills/product-health-analysis/SKILL.md

@@ -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]

plugins/pm-analytics/skills/retention-analysis/SKILL.md

@@ -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*

plugins/pm-business/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-business/skills/board-deck-narrative/SKILL.md

@@ -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]"

plugins/pm-business/skills/investor-update/SKILL.md

@@ -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"

plugins/pm-business/skills/job-application/SKILL.md

@@ -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"

plugins/pm-cross/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-cross",
+  "version": "1.0.0",
+  "description": "Cross-profession skills: Press Release, Grant Proposal, Executive Summary. Write journalist-ready press releases, structure grant applications aligned to funder priorities, and produce decision-ready executive summaries for any audience.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["communications", "press-release", "grant", "executive-summary", "briefing", "funding", "media"]
+}

plugins/pm-cross/skills/executive-summary/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: executive-summary
+description: "Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on."
+---
+
+# Executive Summary Skill
+
+Writes executive summaries that busy decision-makers actually read — front-loaded with conclusions, structured for skimming, ruthless about what to include.
+
+## Required Inputs
+- **Source document or topic** (paste or describe)
+- **Audience** (CEO / board / investor / minister / client / committee)
+- **Decision or action needed** (what should the reader do after reading?)
+- **Length limit** (1 page / 2 pages / 500 words)
+- **Format** (formal report / slide / email / briefing paper)
+
+## Core Principle
+
+An executive summary is NOT a summary of the document. It is a standalone document that:
+- States the conclusion upfront — not at the end
+- Contains only what the reader needs to make a decision
+- Can be understood without reading anything else
+- Recommends a specific action
+
+## Output Structure
+
+---
+
+### [Title]
+**Executive Summary**
+*Prepared for: [Audience] | Date: [Date] | Author: [Name]*
+
+---
+
+**Bottom line up front:**
+[The most important thing. The recommendation or finding. 2-3 sentences. A reader who only reads this should know what you are asking or telling them.]
+
+---
+
+**Background (why this matters):**
+[2-3 sentences. Minimum context to understand the bottom line. Not the history — just what the reader needs now.]
+
+---
+
+**Key findings / analysis:**
+- **[Finding 1]:** [One sentence — specific and evidence-based]
+- **[Finding 2]:** [One sentence]
+- **[Finding 3]:** [One sentence]
+
+---
+
+**Options considered:** (include only if a decision is being presented)
+
+| Option | Benefit | Risk | Recommendation |
+|---|---|---|---|
+| [Option A] | [Benefit] | [Risk] | Recommended |
+| [Option B] | [Benefit] | [Risk] | Not recommended |
+
+---
+
+**Recommendation:**
+[Specific. "We recommend [action] because [reason]. This will [outcome]." Not "we suggest consideration of options."]
+
+---
+
+**Immediate next steps:**
+- [Action 1 — specific, with owner and date]
+- [Action 2]
+
+---
+
+**Risks of inaction:** [What happens if the reader does nothing]
+
+**Full report:** [Reference to where the full document can be found]
+
+---
+
+## Adapting for Different Audiences
+
+**CEO/MD:** Lead with financial or strategic impact. 1 page. Make the decision binary. Ask in sentence one.
+**Board:** Lead with governance or risk. Frame against organisational objectives. State specifically what you need from them.
+**Investor:** Lead with return or opportunity. Specific numbers. 1 page. Anticipate "why now."
+**Minister/senior public sector:** Lead with public benefit or policy alignment. Include cost-benefit framing.
+**Client:** Lead with their problem. Show you understand before presenting recommendation.
+
+## Quality Checks
+- Bottom line in first 3 sentences
+- Standalone — no need to read full document
+- Recommendation is specific
+- Fits length limit
+- Written for audience priorities not author priorities
+- Next steps have owners and dates
+
+## Example Trigger Phrases
+- "Write an executive summary of this report: [paste]"
+- "Summarise this document for the board: [paste]"
+- "Create a one-pager from this proposal for the CEO"
+- "Turn these findings into an exec summary"

plugins/pm-cross/skills/grant-proposal/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: grant-proposal
+description: "Write a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget narrative."
+---
+
+# Grant Proposal Skill
+
+Produces structured grant proposals tailored to the funder priorities — the most common reason grants fail is writing about what you want to do rather than what the funder wants to fund.
+
+## Required Inputs
+- **Funder name and grant programme**
+- **Grant amount sought**
+- **Project description** (rough notes are fine)
+- **Your organisation** (type, track record, capacity)
+- **Funder stated priorities** (copy from their guidance — essential)
+- **Word or page limits**
+- **Deadline**
+
+## Output Structure
+
+---
+
+### Project Title
+[Informative and memorable. Should convey the problem being solved and the approach.]
+
+### 1. Project Summary / Abstract (200-300 words — written last, placed first)
+[What you will do, why it matters, who will benefit, measurable outcomes. Every sentence earns its place.]
+
+### 2. Problem Statement / Need
+- **The problem:** [Specific, evidenced — use data]
+- **Who is affected:** [Population, scale, geography]
+- **Current situation:** [What exists and why it is insufficient]
+- **Consequence of inaction:** [What happens if not funded]
+- **Why your organisation:** [Track record, relationships, expertise]
+
+Funder test: does this problem align with [funder] stated priorities? Make the connection explicit.
+
+### 3. Project Objectives
+3-5 SMART objectives:
+- **Objective 1:** [Specific, Measurable, Achievable, Relevant, Time-bound]
+
+### 4. Methodology / Approach
+
+**Phase 1: [Name]** (Months 1-X)
+[What will happen, who will do it, what is produced]
+
+**Key activities:**
+- [Activity — specific]
+
+**What makes this approach innovative or effective:** [Why this over alternatives]
+
+### 5. Impact and Outcomes
+
+| Level | Description | Measure |
+|---|---|---|
+| Output | [Tangible deliverable] | [How counted] |
+| Short-term outcome | [Immediate change] | [How measured] |
+| Medium-term outcome | [Behaviour change] | [How measured] |
+| Long-term impact | [Systemic change] | [How evidenced] |
+
+**Direct beneficiaries:** [Who and how many]
+**Sustainability:** [How work continues beyond grant period]
+
+### 6. Evaluation Plan
+- Who evaluates, how, when, what is measured, how findings are shared
+
+### 7. Budget Narrative
+
+| Budget line | Amount | Justification |
+|---|---|---|
+| Staff costs | £[amount] | [Role, % FTE, duration, salary] |
+| Travel | £[amount] | [Specific journeys named] |
+| Equipment | £[amount] | [Itemised] |
+| Indirect costs | £[amount] | [[X]% of direct — check policy] |
+| **Total** | **£[total]** | |
+
+**Value for money:** [Cost per beneficiary. What could not be done without this grant]
+
+### 8. Organisational Capacity
+[Track record of similar projects, governance, financial management. Name previous grants and outputs — be specific]
+
+### 9. Risk Register
+
+| Risk | Likelihood | Impact | Mitigation |
+|---|---|---|---|
+| [Risk] | H/M/L | H/M/L | [Specific mitigation] |
+
+---
+
+## Funder Alignment Check
+- Every section explicitly references funder stated priorities
+- Word limits respected
+- Budget aligns with eligible costs policy
+- Required attachments prepared
+
+## Example Trigger Phrases
+- "Write a grant proposal for [project] applying to [funder]"
+- "Help me write a funding application for [grant programme]"
+- "Turn these project notes into a grant proposal: [paste]"

plugins/pm-cross/skills/press-release/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: press-release
+description: "Write a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists."
+---
+
+# Press Release Skill
+
+Writes press releases that journalists actually read — structured around the news angle, not the desire to promote.
+
+## Required Inputs
+- **The news** (what is actually happening — be specific)
+- **Company name**
+- **Date of announcement / embargo date**
+- **Key quote** (from which executive and approximately what they want to say)
+- **Why this matters** (to the reader, not the company)
+- **Target media** (trade / national / local / consumer / investor)
+- **Media contact details**
+
+## Output Structure
+
+---
+
+FOR IMMEDIATE RELEASE / EMBARGOED UNTIL: [Date and time]
+
+---
+
+# [Headline — active verb, specific news, under 10 words]
+## [Subheadline — the so-what in one sentence, adds context not repetition]
+
+**[City, Date]** — [Opening paragraph: Who, What, When, Where, Why in 2-3 sentences. A journalist should be able to run this paragraph alone. No background, no context, no company history.]
+
+[Second paragraph: the significance. Why does this matter? What does it mean for customers or the industry?]
+
+[Third paragraph: quote from executive. Human and specific. Not a restatement of the headline.]
+
+"[Quote text — specific, adds something the facts do not say]," said [Name], [Title] at [Company]. "[Second sentence extending the thought]."
+
+[Fourth paragraph: supporting detail — data, customer names with permission, additional context]
+
+[Fifth paragraph optional: what happens next, when it goes live, what people can do]
+
+---
+
+ENDS
+
+---
+
+**Notes to editors:**
+
+**About [Company]**
+[Boilerplate: 3-4 sentences. What the company does, when founded, where based, key facts. Factual not promotional.]
+
+**Media contact:**
+[Name] | [Title] | [Email] | [Phone] | [Hours/timezone]
+
+---
+
+## Headline Rules
+- Active voice: "Company launches X" not "X is launched by Company"
+- Specific: "raises 5M" not "secures significant investment"
+- Under 10 words
+- Never start with the company name — lead with the news
+
+## Journalist Test
+Would a journalist care? Is the headline the full story? Is there a human angle? Is the quote something a human would say? Can the first paragraph stand alone?
+
+## Example Trigger Phrases
+- "Write a press release announcing [news]"
+- "Draft a media statement about [event]"
+- "We are launching [product] — write the press release"
+- "Turn this announcement into a press release: [paste notes]"

plugins/pm-data/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-data/skills/dashboard-brief/SKILL.md

@@ -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"

plugins/pm-data/skills/metrics-framework/SKILL.md

@@ -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?"

plugins/pm-data/skills/sql-query-explainer/SKILL.md

@@ -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?"

plugins/pm-delivery/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-delivery/skills/ab-test-planner/SKILL.md

@@ -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

plugins/pm-delivery/skills/go-to-market-planner/SKILL.md

@@ -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

plugins/pm-delivery/skills/product-launch-checklist/SKILL.md

@@ -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

plugins/pm-delivery/skills/retro-analysis/SKILL.md

@@ -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]

plugins/pm-delivery/skills/sprint-brief/SKILL.md

@@ -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]

plugins/pm-delivery/skills/sprint-planning/SKILL.md

@@ -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

plugins/pm-delivery/skills/technical-spec-template/SKILL.md

@@ -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

plugins/pm-design/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-design/skills/accessibility-audit/SKILL.md

@@ -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?"

plugins/pm-design/skills/design-critique/SKILL.md

@@ -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]"

plugins/pm-design/skills/ux-research-plan/SKILL.md

@@ -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]"

plugins/pm-discovery/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-discovery/skills/assumption-mapper/SKILL.md

@@ -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

plugins/pm-discovery/skills/discovery-interview-guide/SKILL.md

@@ -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

plugins/pm-discovery/skills/job-story-mapper/SKILL.md

@@ -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"

plugins/pm-discovery/skills/user-interview-synthesis/SKILL.md

@@ -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

plugins/pm-engineering/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-engineering/skills/api-docs-writer/SKILL.md

@@ -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"

plugins/pm-engineering/skills/architecture-decision-record/SKILL.md

@@ -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]"

plugins/pm-engineering/skills/code-review-checklist/SKILL.md

@@ -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"

plugins/pm-engineering/skills/incident-postmortem/SKILL.md

@@ -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]"

plugins/pm-essentials/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-essentials/skills/competitive-analysis/SKILL.md

@@ -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

plugins/pm-essentials/skills/meeting-notes/SKILL.md

@@ -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

plugins/pm-essentials/skills/prd-template/SKILL.md

@@ -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...]
+```

plugins/pm-essentials/skills/stakeholder-update/SKILL.md

@@ -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

plugins/pm-essentials/skills/user-research-synthesis/SKILL.md

@@ -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)
+```

plugins/pm-finance/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-finance",
+  "version": "1.0.0",
+  "description": "Finance skills: Financial Model Narrative, Budget Variance Analysis, Investor Pitch Deck, Financial Due Diligence. Turn numbers into board-ready narratives, explain variances, structure pitch decks, and generate DD checklists.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["finance", "financial-model", "budget", "variance", "pitch-deck", "due-diligence", "investor"]
+}

plugins/pm-finance/skills/budget-variance-analysis/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: budget-variance-analysis
+description: "Produce a structured budget variance analysis from actual vs budget figures. Use when asked to analyse budget variances, explain underspend or overspend, write a variance commentary, or investigate why actuals differ from plan. Produces a categorised variance table with root cause analysis and management commentary."
+---
+
+# Budget Variance Analysis Skill
+
+Produces a complete variance analysis from numbers through to root cause explanation and management commentary.
+
+## Required Inputs
+- **Actuals and budget figures** (paste as table or describe line by line)
+- **Period** (month / quarter / YTD)
+- **Materiality threshold** (e.g. £10k or 5%)
+- **Known reasons for variances** (if any)
+- **Audience** (CFO / board / management / auditor)
+
+## Output Structure
+
+### 1. Variance Summary Table
+
+| Line Item | Budget | Actual | Variance £ | Variance % | F/A |
+|---|---|---|---|---|---|
+| Revenue | | | | | |
+| Cost of Sales | | | | | |
+| Gross Profit | | | | | |
+| Opex | | | | | |
+| EBITDA | | | | | |
+
+F = Favourable | A = Adverse
+
+### 2. Material Variance Commentary
+
+For each variance above threshold:
+
+**[Line item] — £[amount] F/A ([%])**
+- **Root cause:** [Specific explanation — not "timing" without detail]
+- **Permanent or timing?** Will this reverse next period?
+- **Management action:** What is being done
+- **Forecast impact:** Does this change full-year outlook?
+
+### 3. Top 3 Variances Requiring Attention
+Ranked by materiality and strategic significance.
+
+### 4. Forecast Revision
+Does the full-year forecast need updating? State revised expectation and key assumptions.
+
+### 5. Executive Summary
+3-4 sentences of management commentary suitable for a board pack.
+
+## Quality Checks
+- All variances above threshold explained
+- Root causes specific (not vague)
+- Favourable/Adverse correctly labelled
+- Forecast impact stated for material variances
+
+## Example Trigger Phrases
+- "Write a variance analysis for these actuals vs budget: [paste]"
+- "Explain why we are over budget on [cost line]"
+- "Write the variance commentary for our finance review"
+- "Produce a budget vs actual analysis for Q[N]"

plugins/pm-finance/skills/financial-due-diligence/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: financial-due-diligence
+description: "Generate a financial due diligence checklist and analysis framework for any investment, acquisition, or partnership. Use when asked for a due diligence checklist, M&A financial review, investment analysis framework, or vendor financial assessment."
+---
+
+# Financial Due Diligence Skill
+
+Produces a structured financial due diligence framework — document request list and analytical questions — for any investment, acquisition, or significant commercial relationship.
+
+## Required Inputs
+- **Transaction type** (acquisition / investment / partnership / supplier / fundraise)
+- **Stage of diligence** (initial screening / full DD / confirmatory)
+- **Target company type** (startup / SME / listed / subsidiary)
+- **Key concerns** (optional — e.g. revenue recognition, customer concentration)
+
+## Output Structure
+
+### 1. Document Request List
+
+**Financial Statements**
+- Audited accounts for last 3 years
+- Management accounts for current year (monthly)
+- Board-approved budget and latest reforecast
+- 3-year financial model with assumptions
+
+**Revenue**
+- Revenue by customer (top 20, % of total)
+- Revenue by product/segment
+- Contracted vs recurring vs one-off breakdown
+- Churn and renewal data
+
+**Costs**
+- Cost of sales breakdown
+- Headcount by department with compensation detail
+- Top 10 supplier contracts
+
+**Cash and Debt**
+- Bank statements (12 months)
+- Debt schedule with covenants and maturity
+- Working capital analysis
+
+**Tax**
+- Last 3 years tax returns
+- Any open enquiries
+- R&D tax credit claims
+
+### 2. Key Analytical Questions
+
+**Revenue quality:** Is revenue growing organically? What % is truly recurring? Customer concentration risk?
+
+**Margin analysis:** Gross margin trend over 3 years? One-off items inflating EBITDA? Normalised EBITDA?
+
+**Cash conversion:** Does profit convert to cash? Cash conversion cycle? Working capital red flags?
+
+**Debt and liabilities:** Net debt position? Contingent liabilities? Covenant headroom?
+
+### 3. Red Flags Checklist
+- Revenue concentration over 30% in one customer
+- Declining gross margins without explanation
+- EBITDA-to-cash conversion below 70%
+- Auditor qualifications or emphasis of matter
+- Related party transactions not at arm length
+- Aggressive revenue recognition
+- Growing debtor days with no explanation
+
+### 4. Summary Output Template
+- Revenue quality: [Assessment]
+- Margin sustainability: [Assessment]
+- Cash generation: [Assessment]
+- Balance sheet risk: [Assessment]
+- Overall: Green Strong / Amber Acceptable / Red Material concerns
+
+## Example Trigger Phrases
+- "Give me a financial due diligence checklist for [company type]"
+- "What documents should I request for financial DD?"
+- "Build a DD framework for our Series A investment"

plugins/pm-finance/skills/financial-model-narrative/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: financial-model-narrative
+description: "Turn financial model outputs into a clear written narrative. Use when asked to write a financial narrative, explain a financial model, summarise a P&L, or translate spreadsheet numbers into a board-ready story. Produces an executive narrative with key insights, drivers, and forward-looking commentary."
+---
+
+# Financial Model Narrative Skill
+
+Turns financial model outputs into a clear, structured written narrative suitable for board packs, investor updates, or management reporting.
+
+## Required Inputs
+- **Financial data** (paste key figures: revenue, costs, margins, EBITDA, cash)
+- **Period covered** (month / quarter / annual / multi-year)
+- **Audience** (board / investors / management / bank / internal)
+- **Key message** (what is the headline story?)
+- **Actuals vs budget / prior period?** (comparison context)
+
+## Output Structure
+
+### 1. Headline Summary
+3-5 sentences. The financial story in plain English. Lead with the most important insight — not "revenue was X" but what that figure means.
+
+### 2. Revenue
+- Performance vs prior period / budget
+- Key drivers: what caused the movement
+- Risks or opportunities in the revenue line
+
+### 3. Costs and Margins
+- Gross margin: % and trend
+- Key cost movements and why
+- EBITDA performance and drivers
+- One-off items clearly flagged
+
+### 4. Cash and Balance Sheet
+- Cash position and movement
+- Runway (for startups)
+- Key working capital movements
+
+### 5. Variance Analysis
+For each significant variance:
+
+**[Line item] — Over/Under by [amount]**
+- **Cause:** [Plain English explanation]
+- **Permanent or temporary?** One-time / Structural
+- **Action being taken:** [If applicable]
+
+### 6. Forward-Looking Commentary
+- Expected next period
+- Key risks to forecast
+- Key opportunities
+- Any reforecast or guidance change
+
+## Writing Rules
+- Never just restate a number — always explain what it means
+- Flag variances over 10% automatically
+- Use past tense for actuals, conditional for forecast
+- One insight per paragraph
+
+## Example Trigger Phrases
+- "Write a financial narrative for these results: [paste numbers]"
+- "Turn this P&L into a board narrative"
+- "Write the finance section of our board pack"
+- "Explain these financial results in plain English"

plugins/pm-finance/skills/investor-pitch-deck/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: investor-pitch-deck
+description: "Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor."
+---
+
+# Investor Pitch Deck Skill
+
+Builds the complete narrative and slide structure for an investor pitch deck — focused on what investors need to see, not what founders want to show.
+
+## Required Inputs
+- **Company name and one-line description**
+- **Stage** (Pre-seed / Seed / Series A / Series B)
+- **Ask** (how much raising and what for)
+- **Key metrics** (revenue, growth, users, retention)
+- **Target investors** (generalist / sector-specific / angels)
+- **Deck length** (10 / 12 / 15 slides)
+
+## Output Structure
+
+For each slide:
+- **What this slide must prove** (the investor question it answers)
+- **Content guidance** (specific, not generic)
+- **Common mistake to avoid**
+
+---
+
+**Slide 1: Cover** — Proves you can say what you do in one sentence.
+**Slide 2: Problem** — Proves the problem is real, painful, and large. Lead with the human problem, not market size.
+**Slide 3: Solution** — Proves your solution is meaningfully better. Focus on outcome, not features.
+**Slide 4: Product** — Proves this is real and works. Show the actual product.
+**Slide 5: Traction** — Proves people want this. Show retention and revenue, not signups.
+**Slide 6: Market** — Proves the market is large enough. Use bottoms-up TAM where possible.
+**Slide 7: Business Model** — Proves you understand unit economics. Include CAC and LTV.
+**Slide 8: Go-To-Market** — Proves you can acquire customers efficiently. Focus on what is actually working.
+**Slide 9: Competition** — Proves you understand the landscape. Never say "no competitors."
+**Slide 10: Team** — Proves this team can execute this opportunity. One sentence per person, specific.
+**Slide 11: Financials** — Proves you understand your business. Show assumptions, not just projections.
+**Slide 12: The Ask** — Proves you know exactly what you need. Specific use of funds and 18-month milestones.
+
+## Narrative Principles
+- Every slide answers one investor question
+- Investors decide go/no-go on slides 1-5 — front-load evidence
+- Keep to 10-12 slides for a first meeting
+
+## Example Trigger Phrases
+- "Build a pitch deck structure for [company]"
+- "Help me structure my Series A deck"
+- "What slides should my investor pitch have?"

plugins/pm-gtm/.claude-plugin/plugin.json

@@ -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"]
+}

plugins/pm-gtm/skills/competitor-teardown/SKILL.md

@@ -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]"

plugins/pm-gtm/skills/content-calendar/SKILL.md

@@ -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"

plugins/pm-gtm/skills/email-campaign/SKILL.md

@@ -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"

plugins/pm-gtm/skills/go-to-market/SKILL.md

@@ -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"

plugins/pm-hr/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-hr",
+  "version": "1.0.0",
+  "description": "HR skills: Job Description Writer, Onboarding Plan, Employee Engagement Survey, Redundancy Consultation. Write inclusive JDs, build 30/60/90-day plans, design engagement surveys, and structure legally compliant redundancy processes.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["hr", "people", "job-description", "onboarding", "engagement", "redundancy", "recruitment"]
+}

plugins/pm-hr/skills/employee-engagement-survey/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: employee-engagement-survey
+description: "Design an employee engagement survey and analyse results. Use when asked to create an employee survey, engagement questionnaire, pulse survey, or eNPS survey. Also use when asked to analyse survey results. Produces a complete survey with questions, rating scales, and an analysis framework."
+---
+
+# Employee Engagement Survey Skill
+
+Designs complete employee engagement surveys and provides a framework for analysing and acting on results.
+
+## Mode Detection
+- User provides survey results -> Analysis mode
+- User wants to create a survey -> Design mode
+
+---
+
+## Design Mode
+
+### Required Inputs
+- Survey type (annual / quarterly pulse / post-onboarding / exit / specific topic)
+- Company size and stage
+- Key areas of concern (optional)
+- Anonymity approach
+- Length target (short: 5-10 / standard: 15-25 / comprehensive: 30+)
+
+### Opening Statement (always include)
+"This survey is anonymous. Your responses help us understand what is working and what to improve. Results will be shared with [who] and we will communicate actions taken by [date]."
+
+### Core Questions
+
+**Overall Engagement**
+1. On a scale of 0-10, how likely are you to recommend [Company] as a great place to work? (eNPS)
+2. I feel proud to work at [Company]. [1-5]
+3. I intend to still be working here in 12 months. [1-5]
+
+**Role and Clarity**
+4. I understand how my work contributes to company goals. [1-5]
+5. I have the tools and resources I need to do my job. [1-5]
+6. My workload is manageable. [1-5]
+
+**Manager and Team**
+7. My manager gives useful feedback. [1-5]
+8. My manager cares about my development. [1-5]
+9. I feel part of a team that works well together. [1-5]
+
+**Culture and Belonging**
+10. I feel I can be myself at work. [1-5]
+11. People treat each other with respect. [1-5]
+12. [Company] lives by its stated values. [1-5]
+
+**Growth and Recognition**
+13. I have opportunities to grow and develop. [1-5]
+14. My contributions are recognised. [1-5]
+15. I have had a meaningful career conversation in the last 6 months. [Yes/No]
+
+**Open questions (always include)**
+- What is one thing [Company] should start doing?
+- What is one thing [Company] should stop doing?
+- Anything else to share?
+
+---
+
+## Analysis Mode
+
+### Analysis Output
+
+**1. Headline Scores**
+| Metric | Score | Benchmark | Trend |
+|---|---|---|---|
+| eNPS | [-100 to +100] | Industry avg | vs last survey |
+
+eNPS: Below 0 = Concerning / 0-30 = Good / 30-70 = Great / 70+ = Excellent
+
+**2. Strengths** — Top scoring areas with evidence.
+
+**3. Improvement Areas** — 3 lowest scoring areas with verbatim comment themes.
+
+**4. Action Planning Template**
+| Improvement area | Action | Owner | Timeline | Measure |
+|---|---|---|---|---|
+
+**5. Communication Template** — Draft message to share results with employees.
+
+## Example Trigger Phrases
+- "Create an employee engagement survey for our team"
+- "Design a pulse survey for [topic]"
+- "Analyse these engagement survey results: [paste]"

plugins/pm-hr/skills/job-description-writer/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: job-description-writer
+description: "Write a clear, inclusive, and structured job description for any role. Use when asked to write a job description, job posting, JD, or job advert. Produces a complete JD with role summary, responsibilities, requirements, and inclusive language review."
+---
+
+# Job Description Writer Skill
+
+Writes complete, inclusive job descriptions that attract the right candidates and reduce bias in the hiring process.
+
+## Required Inputs
+- **Job title and level**
+- **Team and reporting line**
+- **Top 5 things this person will actually do**
+- **Must-have requirements** (be ruthless — only what is truly required)
+- **Nice-to-have requirements**
+- **Salary range** (JDs with salary ranges get 30% more applicants)
+- **Location and remote policy**
+- **Company description** (2-3 sentences)
+
+## Output Structure
+
+### [Job Title]
+**[Company] | [Location] | [Remote policy] | [Salary range]**
+
+**About [Company]**
+[2-3 sentences. Specific and honest — not marketing copy.]
+
+**The Role**
+[3-4 sentences. What this person will own, why the role exists now, what success looks like in year one.]
+
+**What You Will Do**
+[6-8 bullet points. Outcomes and responsibilities, not activities. Start each with an action verb. Most important first.]
+
+**What We Are Looking For**
+
+Must have (4-6 items only):
+- [Requirement]
+
+Nice to have (3-4 items):
+- [Nice to have]
+
+**What We Offer**
+[Compensation, benefits, development. Be specific.]
+
+**How to Apply**
+[Clear instructions. What to send, where, timeline.]
+
+---
+
+### Inclusive Language Review
+
+**Words to remove or replace:**
+
+| Original | Replace with | Why |
+|---|---|---|
+| "rockstar" | "experienced" | Gendered connotation |
+| "ninja" | "skilled" | Same issue |
+| "must have degree" | "relevant experience or qualification" | Excludes qualified non-graduates |
+
+**Requirement audit:**
+- Years of experience requirements flagged (screen out women and underrepresented groups disproportionately)
+- Any requirements potentially discriminating against protected characteristics
+
+## Quality Checks
+- Salary range included
+- Must-haves genuinely essential (6 items max)
+- Each responsibility starts with action verb
+- Inclusive language review completed
+- No years-of-experience requirements unless legally required
+
+## Example Trigger Phrases
+- "Write a job description for a [role]"
+- "Create an inclusive job posting for [role]"
+- "Review and rewrite this JD: [paste]"

plugins/pm-hr/skills/onboarding-plan/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: onboarding-plan
+description: "Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria."
+---
+
+# Onboarding Plan Skill
+
+Creates a complete, structured onboarding plan tailored to a specific role — covering the first 90 days with clear milestones and success criteria.
+
+## Required Inputs
+- **Role and level** of the new hire
+- **Team and manager**
+- **Key stakeholders** they will work with
+- **Top 3 priorities** for their first 90 days
+- **Tools and systems** they will need access to
+- **Company stage** (startup / scaleup / enterprise)
+
+## Output Structure
+
+### Onboarding Plan: [Name] — [Role]
+**Start date:** [Date] | **Manager:** [Name] | **Buddy:** [Name]
+
+---
+
+### Before Day 1 (Manager checklist)
+- IT setup: laptop, accounts, email, Slack, key tools
+- Access provisioned to key systems
+- First week calendar blocked with key meetings
+- Buddy assigned and briefed
+- Welcome message sent with Day 1 logistics
+
+---
+
+### Week 1: Orient
+Theme: Listen, learn, do not act yet.
+
+| Day | Focus | Key activities |
+|---|---|---|
+| Day 1 | IT setup, team intro | 1:1 with manager, team lunch |
+| Day 2 | Product deep dive | Demo, key docs to read |
+| Day 3 | Process and tools | Shadow key workflows |
+| Day 4 | Stakeholder intros | 3-4 intro 1:1s |
+| Day 5 | Week 1 debrief | Check-in, questions logged |
+
+**Week 1 milestone:** Can describe what the company does, the team role, and their top 3 priorities.
+
+---
+
+### Days 8-30: Learn
+Learning goals:
+- Deep understanding of product from customer perspective
+- Know key metrics the team is measured on
+- Understand current projects and status
+- Map key stakeholder relationships
+- Complete all compliance/HR training
+
+**30-day milestone:** All stakeholder 1:1s complete. 2-3 early observations shared with manager.
+
+---
+
+### Days 31-60: Contribute
+Goals:
+- Own at least one project end-to-end
+- Make one meaningful contribution
+- Build cross-functional relationships
+- Identify one process improvement
+
+**60-day milestone:** Delivered one tangible output. Manager says "this person is contributing."
+
+---
+
+### Days 61-90: Lead
+Goals:
+- Operating independently on core responsibilities
+- Has formed and shared a point of view on priorities
+- Building reputation with key stakeholders
+
+**90-day milestone:** Ready for formal review. Clear 6-month plan in place.
+
+---
+
+### 90-Day Review Questions
+Manager: Meeting expectations? What to double down on? What to develop?
+New hire: Have the clarity, tools, support needed? What surprised you? What would you change about onboarding?
+
+## Example Trigger Phrases
+- "Create a 30/60/90 day plan for a new [role]"
+- "Write an onboarding plan for [name] starting as [role]"
+- "Build a first 90 days roadmap for our new hire"

plugins/pm-hr/skills/redundancy-consultation/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: redundancy-consultation
+description: "Structure a redundancy consultation process and draft key communications. Use when asked to plan a redundancy process, write a redundancy letter, structure a consultation, or manage a reduction in force. UK employment law focus. Always recommend qualified HR/legal advice before proceeding."
+---
+
+# Redundancy Consultation Skill
+
+Structures redundancy processes and drafts communications. Significant legal and human risk — always flag that employment legal advice is essential before proceeding.
+
+WARNING: Defaults to UK employment law (Employment Rights Act 1996). Always recommend qualified HR/legal advice before any redundancy action.
+
+## Required Inputs
+- **Number of roles affected** (1-19 = individual; 20+ = collective consultation required)
+- **Reason for redundancy** (genuine business reason)
+- **Jurisdiction** (UK / US / EU / Other)
+- **Timeline constraints**
+- **Selection pool** (if multiple people in similar roles)
+
+## Output Structure
+
+### 1. Process Overview
+
+**Individual redundancy (fewer than 20):**
+| Stage | Action | Minimum timeline |
+|---|---|---|
+| 1 | Confirm business case internally | Before any communication |
+| 2 | At-risk notification meeting | Day 1 |
+| 3 | Individual consultation | Minimum 1 meaningful meeting |
+| 4 | Redundancy confirmed or alternative found | After genuine consideration |
+| 5 | Notice period begins | Per contract |
+| 6 | Final day and payment | Per contract + statutory |
+
+**Collective redundancy (20+ roles — UK):**
+- Minimum 45 days consultation before first dismissal
+- Must notify BEIS (HR1 form) before consultation begins
+- Employee representatives must be elected if no union recognised
+- Failure = unlimited protective award per employee
+
+### 2. Selection Criteria (if pool exists)
+Objective, non-discriminatory only: skills/qualifications, performance (documented evidence), attendance (exclude disability/pregnancy-related absences), length of service (tiebreaker only).
+
+NEVER select on: age, disability, pregnancy/maternity, part-time status, trade union membership.
+
+### 3. At-Risk Letter Draft
+"Dear [Name], I am writing to inform you that your role of [Job Title] is at risk of redundancy. This is because [specific business reason]. We would like to meet on [date] to discuss the situation and explore alternatives. You have the right to be accompanied by a colleague or trade union representative. No decision has been made. Yours sincerely, [Manager]"
+
+### 4. Consultation Meeting Script
+Opening: "No decision has been made. This meeting is to explain the situation and listen to your views."
+Key questions: Any ways to avoid this? Alternative roles of interest? Anything about selection to challenge?
+
+### 5. Redundancy Confirmation Letter Draft
+Issued only after genuine consultation. Must include: statutory pay calculated, notice period, payment for accrued holiday, right of appeal.
+
+### 6. Statutory Redundancy Pay Guide (UK)
+- Under 22: 0.5 week per year of service
+- 22-40: 1 week per year of service
+- 41+: 1.5 weeks per year of service
+- Weekly pay capped (verify current rate)
+- Maximum 20 years counts
+
+---
+
+WARNING: Take advice from an employment lawyer or qualified HR professional before beginning any redundancy process.
+
+## Example Trigger Phrases
+- "Help me structure a redundancy consultation"
+- "Draft an at-risk letter for [role]"
+- "What is the process for making someone redundant in the UK?"

plugins/pm-legal/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-legal",
+  "version": "1.0.0",
+  "description": "Legal skills: Contract Review, NDA Analyser, Legal Brief, Compliance Checklist. Flag risks in contracts and NDAs, draft legal memos in IRAC format, and generate GDPR, SOC 2, FCA and other compliance checklists. Not a substitute for qualified legal advice.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["legal", "contract-review", "nda", "compliance", "gdpr", "legal-brief", "risk"]
+}

plugins/pm-legal/skills/compliance-checklist/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: compliance-checklist
+description: "Generate a compliance checklist for any regulation, standard, or policy. Use when asked to create a compliance checklist, regulatory review, audit checklist, or policy adherence review. Covers GDPR, ISO 27001, FCA, HIPAA, SOC 2, and other frameworks. Produces a prioritised checklist with pass/fail assessment and remediation actions."
+---
+
+# Compliance Checklist Skill
+
+Generates a structured compliance checklist for any regulatory framework with a prioritised gap analysis and remediation actions.
+
+## Required Inputs
+- **Framework or regulation** (e.g. GDPR, HIPAA, SOC 2, ISO 27001, FCA Consumer Duty, PCI DSS)
+- **Organisation type** (e.g. SaaS company, financial services, NHS trust, law firm)
+- **Scope** (e.g. data handling, customer onboarding, IT security, HR processes)
+- **Known gaps or concerns** (optional)
+
+## Output Structure
+
+### 1. Framework Overview
+- **Regulation/Standard:** [Name and version]
+- **Enforcement body:** [Regulator]
+- **Overall compliance status:** Red Gaps / Amber Partial / Green Compliant
+
+### 2. Compliance Checklist
+
+| # | Requirement | Status | Priority | Action Required |
+|---|---|---|---|---|
+| 1 | [Plain English requirement] | Met / Gap / Partial / Unknown | Critical / High / Low | [Specific action] |
+
+Priority definitions:
+- Critical: Regulatory breach risk. Remediate immediately.
+- High: Significant gap. Address within 30 days.
+- Low: Best practice. Address in next review cycle.
+
+### 3. Critical Gaps Summary
+List only Critical items with: what is missing, regulatory requirement breached, recommended remediation and owner.
+
+### 4. Recommended Remediation Plan
+
+| Action | Owner | Timeline | Effort |
+|---|---|---|---|
+| [Specific action] | [Team/role] | [Timeframe] | Low/Med/High |
+
+### 5. Documentation Gaps
+Policies, records, or evidence needed to demonstrate compliance.
+
+---
+
+WARNING: This checklist is a starting point based on publicly available guidance. It does not constitute legal or compliance advice.
+
+## Example Trigger Phrases
+- "Create a GDPR compliance checklist for our SaaS product"
+- "Generate a SOC 2 audit checklist"
+- "Review our compliance against FCA Consumer Duty"
+- "Build an ISO 27001 gap analysis"

plugins/pm-legal/skills/contract-review/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: contract-review
+description: "Review and summarise any contract or legal agreement. Use when asked to review a contract, check an agreement, flag legal risks, or summarise key clauses. Produces a structured review with key terms, flagged clauses, risk rating, and plain English summary. Not a substitute for qualified legal advice."
+---
+
+# Contract Review Skill
+
+This skill produces a structured contract review identifying key terms, unusual or high-risk clauses, and a plain English summary. Always include the disclaimer that this is not legal advice.
+
+## Required Inputs
+- **Contract text or description** (paste or describe)
+- **Reviewer role** (e.g. the party signing, their legal team, a business owner)
+- **Contract type** (e.g. SaaS agreement, employment contract, NDA, supplier contract)
+- **Key concerns** (optional — e.g. "focus on IP ownership and termination clauses")
+
+## Output Structure
+
+### 1. Contract Overview
+- **Type:** [Contract type]
+- **Parties:** [Party A and Party B]
+- **Effective date / duration:** [If stated]
+- **Governing law:** [Jurisdiction]
+- **Overall risk rating:** Green Low / Amber Medium / Red High
+
+### 2. Key Terms Summary
+
+| Term | Detail |
+|---|---|
+| Payment / fees | |
+| Term and renewal | |
+| Termination rights | |
+| Liability cap | |
+| IP ownership | |
+| Confidentiality | |
+| Dispute resolution | |
+
+### 3. Flagged Clauses
+
+For each flagged clause:
+
+**[Risk level] — [Clause name]**
+- **What it says:** [Plain English summary]
+- **Why it matters:** [Risk or implication]
+- **Suggested action:** [Negotiate / Accept / Seek legal advice / Query]
+
+### 4. Missing Clauses
+List any standard clauses absent but normally expected for this contract type.
+
+### 5. Plain English Summary
+3-5 sentences. What does this contract mean for the party signing it?
+
+### 6. Recommended Next Steps
+- [Action 1]
+- [Action 2]
+
+---
+
+WARNING: This review is for informational purposes only and does not constitute legal advice. Always consult a qualified solicitor or lawyer before signing any legally binding agreement.
+
+## Example Trigger Phrases
+- "Review this contract: [paste]"
+- "Flag the key risks in this agreement"
+- "Summarise this SaaS contract in plain English"
+- "What should I watch out for in this supplier agreement?"

plugins/pm-legal/skills/legal-brief/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: legal-brief
+description: "Draft a structured legal brief, case summary, or legal argument outline. Use when asked to write a legal brief, case note, legal memo, argument outline, or position paper. Produces a structured document using IRAC format (Issue, Rule, Application, Conclusion)."
+---
+
+# Legal Brief Skill
+
+This skill drafts structured legal briefs and memos using IRAC format — the standard structure for legal writing.
+
+## Required Inputs
+- **Brief type** (legal memo / case summary / argument outline / position paper / letter before action)
+- **Legal issue or question**
+- **Jurisdiction** (England & Wales / US / EU / Other)
+- **Relevant facts**
+- **Relevant law or cases** (if known — otherwise flagged as [RESEARCH NEEDED])
+- **Audience** (internal memo / court submission / client letter)
+
+## Output Structure
+
+### Header
+- **To:** [Recipient]
+- **From:** [Author]
+- **Date:** [Date]
+- **Re:** [Matter reference]
+- **Confidential:** Subject to legal professional privilege
+
+### Issue(s)
+One sentence per legal question:
+- Issue 1: Whether X constitutes Y under [law]
+
+### Brief Answer
+One sentence per issue — conclusion upfront before analysis.
+
+### Facts
+Concise relevant facts only. Flag disputed facts.
+
+### Law (Rule)
+- Relevant statute, regulation, or case law
+- How the rule has been interpreted in key cases
+- Flag [RESEARCH NEEDED] where law is not provided
+
+### Application
+- Arguments in favour
+- Counter-arguments and responses
+- Areas of uncertainty flagged explicitly
+
+### Conclusion
+- Clear answer to each issue
+- Overall recommendation
+- Suggested next steps
+
+### Caveats
+What this memo does not cover. What additional research would change the analysis.
+
+---
+
+WARNING: This draft requires review by a qualified legal professional. It does not constitute legal advice.
+
+## Example Trigger Phrases
+- "Draft a legal memo on [issue]"
+- "Write a legal brief arguing [position]"
+- "Summarise the legal position on [topic]"
+- "Write a letter before action for [situation]"

plugins/pm-legal/skills/nda-analyser/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: nda-analyser
+description: "Analyse a Non-Disclosure Agreement (NDA) and flag key terms, unusual provisions, and negotiation points. Use when asked to review an NDA, mutual NDA, confidentiality agreement, or non-disclosure deed. Produces clause-by-clause analysis with risk flags and a negotiation checklist."
+---
+
+# NDA Analyser Skill
+
+NDAs are often treated as routine paperwork but contain terms with significant long-term consequences. This skill analyses them systematically.
+
+## Required Inputs
+- **NDA text** (paste in full or describe key clauses)
+- **Your party position** (disclosing / receiving / mutual)
+- **Purpose of the NDA** (e.g. pre-sales, hiring, M&A, partnership)
+- **Industry context** (optional)
+
+## Output Structure
+
+### 1. NDA Type and Parties
+- **Type:** Unilateral / Mutual
+- **Disclosing party:** [Name]
+- **Receiving party:** [Name]
+- **Purpose:** [As stated]
+- **Governing law:** [Jurisdiction]
+- **Term:** [Duration of obligations]
+
+### 2. Definition of Confidential Information
+- **How broadly defined?** Narrow / Standard / Very broad
+- **Oral disclosures included?** Yes / No / With conditions
+- **Standard exclusions present?** [public domain, prior knowledge, independently developed, legally required disclosure]
+- **Flag:** [Unusual inclusions or missing exclusions]
+
+### 3. Key Clause Analysis
+
+**[Clause name] — Concern / Watch / Standard**
+- **What it says:** [Plain English]
+- **Issue:** [Why flagged]
+- **Standard position:** [What this typically looks like]
+- **Negotiation suggestion:** [If applicable]
+
+Clauses always covered: permitted use, non-solicitation/non-compete, term and post-termination obligations, return/destruction of information, remedies, liability, residuals clause.
+
+### 4. Negotiation Checklist
+
+| Point | Current position | Suggested ask |
+|---|---|---|
+| [e.g. Confidentiality term] | [e.g. 5 years] | [e.g. Reduce to 2 years] |
+
+### 5. Plain English Verdict
+2-3 sentences. Standard NDA, one-sided, or needs a lawyer?
+
+---
+
+WARNING: This analysis is for informational purposes only and is not legal advice. Consult a qualified solicitor before signing.
+
+## Example Trigger Phrases
+- "Analyse this NDA"
+- "Review this confidentiality agreement"
+- "Is this NDA standard or unusual?"
+- "What should I negotiate in this mutual NDA?"

plugins/pm-operations/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
+  "name": "pm-operations",
+  "version": "1.0.0",
+  "description": "Operations skills: Process Documentation, SOP Writer, Vendor Evaluation, Project Status Report. Document workflows, write audit-ready SOPs, evaluate vendors with weighted scorecards, and produce RAG status reports.",
+  "author": {
+    "name": "Mohit Aggarwal",
+    "email": "mohit15856@gmail.com"
+  },
+  "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
+  "license": "MIT",
+  "keywords": ["operations", "process", "sop", "vendor", "procurement", "project-management", "rag-status"]
+}

plugins/pm-operations/skills/process-documentation/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: process-documentation
+description: "Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases."
+---
+
+# Process Documentation Skill
+
+Produces clear, structured process documentation that someone new to a role can follow without needing to ask questions.
+
+## Required Inputs
+- **Process name**
+- **Process description** (rough notes are fine)
+- **Who does this process** (roles involved)
+- **How often it runs** (daily / weekly / monthly / event-triggered)
+- **Tools involved**
+- **Known edge cases**
+
+## Output Structure
+
+---
+
+# Process: [Process Name]
+**Owner:** [Role] | **Frequency:** [How often] | **Estimated time:** [Duration]
+
+---
+
+### Purpose
+[1-2 sentences. Why does this process exist? What breaks if it is not done?]
+
+### Scope
+**In scope:** [What this covers]
+**Out of scope:** [What it does not cover]
+
+### Prerequisites
+- [ ] [Required access or information]
+- [ ] [Any dependency that must be completed first]
+
+---
+
+### Roles and Responsibilities
+
+| Role | Responsibility |
+|---|---|
+| [Role 1] | [What they do] |
+
+---
+
+### Process Steps
+
+**Step 1: [Step name]**
+- **Who:** [Role]
+- **When:** [Trigger or timing]
+- **How:** [Substeps numbered]
+- **Output:** [What exists at end of this step]
+- **Tool:** [System used]
+
+[Continue for all steps]
+
+---
+
+### Edge Cases and Exceptions
+
+| Situation | What to do | Who to contact |
+|---|---|---|
+| [Edge case] | [Action] | [Name/role] |
+
+---
+
+### Common Mistakes
+[2-4 things people get wrong the first time]
+
+### Escalation Path
+[Name/role] → [Next level] → [Final escalation]
+
+### Review
+Next review due: [Date]
+
+## Example Trigger Phrases
+- "Document this process: [description]"
+- "Write a process guide for [workflow]"
+- "Map out how [process] works"

plugins/pm-operations/skills/project-status-report/SKILL.md

@@ -0,0 +1,109 @@
+---
+name: project-status-report
+description: "Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed."
+---
+
+# Project Status Report Skill
+
+Produces a clear, structured project status report — the weekly communication that keeps stakeholders informed without requiring a meeting.
+
+## Required Inputs
+- **Project name**
+- **Reporting period**
+- **Current RAG status** (Red / Amber / Green)
+- **Key milestones** (due, delivered, coming)
+- **Issues or blockers**
+- **Decisions needed from stakeholders**
+- **Budget status** (if tracked)
+- **Audience** (steering committee / sponsor / PMO / full team)
+
+## Output Structure
+
+---
+
+# Project Status Report: [Project Name]
+**Period:** [Date range] | **Author:** [PM] | **Next report:** [Date]
+
+---
+
+### Overall Status
+
+| Dimension | Status | Last period | Trend |
+|---|---|---|---|
+| Overall | Red / Amber / Green | [Last] | Improving / Stable / Declining |
+| Schedule | | | |
+| Budget | | | |
+| Scope | | | |
+| Risks | | | |
+
+RAG definitions:
+- Green: On track. No significant issues.
+- Amber: At risk. Issues identified but mitigations in place.
+- Red: Off track. Escalation or decisions required to recover.
+
+---
+
+### Executive Summary
+[3-5 sentences. Headline story. If it is Red, say so immediately and why. Never bury bad news after good news.]
+
+---
+
+### Milestone Progress
+
+| Milestone | Due date | Status | Comment |
+|---|---|---|---|
+| [Milestone] | [Date] | Complete / At risk / Delayed / On track | [One line] |
+
+**Completed this period:** [What was delivered]
+**Due next period:** [What is expected]
+
+---
+
+### Issues and Blockers
+
+**[Issue title] — Critical / High / Low**
+- **Description:** [What the issue is]
+- **Impact:** [What happens if unresolved]
+- **Owner:** [Who is resolving]
+- **Action:** [What is being done]
+- **Resolution date:** [When it will be closed]
+
+---
+
+### Risks
+
+| Risk | Likelihood | Impact | Mitigation | Owner |
+|---|---|---|---|---|
+| [Risk] | H/M/L | H/M/L | [Action] | [Name] |
+
+---
+
+### Decisions Required
+
+| Decision | Background | Options | Recommendation | Needed by |
+|---|---|---|---|---|
+| [Decision] | [Context] | [Options] | [Recommendation] | [Date] |
+
+---
+
+### Budget Summary
+
+| | Budget | Actual to date | Forecast | Variance |
+|---|---|---|---|---|
+| Total | £ | £ | £ | £ F/A |
+
+---
+
+### Next Period Plan
+[3-5 specific bullet points — what will happen next period]
+
+## Writing Rules
+- Never soften a Red status
+- Milestones are binary: complete or not complete
+- Decisions must be genuinely actionable
+- Keep to one page where possible
+
+## Example Trigger Phrases
+- "Write a project status report for [project]"
+- "Generate a RAG status update for [project]"
+- "Write the steering committee report for [project]"

plugins/pm-operations/skills/sop-writer/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: sop-writer
+description: "Write a Standard Operating Procedure (SOP) for any operational task. Use when asked to write an SOP, standard operating procedure, work instruction, or operating manual. Produces a formal SOP with purpose, scope, procedure steps, quality checks, and version control."
+---
+
+# SOP Writer Skill
+
+Produces formal, audit-ready SOPs suitable for regulated industries, ISO certification, or operational scaling.
+
+## Required Inputs
+- **SOP title** (e.g. "SOP-001: New Client Onboarding")
+- **Department / function**
+- **Process description**
+- **Regulatory or quality standard** (ISO 9001, GMP, CQC, FCA, etc.)
+- **Roles involved**
+- **Tools or equipment used**
+
+## Output Structure
+
+---
+
+**[COMPANY NAME] — Standard Operating Procedure**
+
+| Document ID | [SOP-XXX] |
+|---|---|
+| Title | [Title] |
+| Department | [Department] |
+| Version | 1.0 |
+| Effective date | [Date] |
+| Review date | [Date] |
+| Status | Draft / Under review / Approved |
+
+---
+
+### 1. Purpose
+[1-2 sentences. Why does this SOP exist?]
+
+### 2. Scope
+**Applies to:** [Roles, departments, locations]
+**Does not apply to:** [Explicit exclusions]
+
+### 3. Definitions
+| Term | Definition |
+|---|---|
+| [Term] | [Plain English definition] |
+
+### 4. Responsibilities
+| Role | Responsibility |
+|---|---|
+| [Role] | [Specific responsibility] |
+
+### 5. Required Materials / Tools / Access
+- [Item]
+
+### 6. Procedure
+
+| Step | Action | Responsible | Record/Output |
+|---|---|---|---|
+| 6.1.1 | [Imperative action: "Open [system] and navigate to [location]"] | [Role] | [What to record] |
+
+NOTE: Steps must be written in imperative form. Each step must have one action only.
+
+### 7. Quality Checks
+
+| Check point | What to verify | Pass criteria | If fail |
+|---|---|---|---|
+| [After step X] | [What to check] | [What good looks like] | [What to do] |
+
+### 8. Non-Conformance
+1. [Immediate action]
+2. [Who to notify]
+3. [How to document deviation]
+
+### 9. References
+[Related SOPs, policies, standards]
+
+### 10. Document History
+
+| Version | Date | Author | Changes |
+|---|---|---|---|
+| 1.0 | [Date] | [Name] | Initial release |
+
+## Quality Checks
+- All steps in imperative form
+- Each step has exactly one action
+- Roles specified for every step
+- Quality checkpoints at critical stages
+- Non-conformance process defined
+
+## Example Trigger Phrases
+- "Write an SOP for [process]"
+- "Create a standard operating procedure for [task]"
+- "Write a work instruction for [process]"

plugins/pm-operations/skills/vendor-evaluation/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: vendor-evaluation
+description: "Create a structured vendor evaluation framework for any procurement decision. Use when asked to evaluate vendors, compare suppliers, run an RFP scoring process, or assess a software or service provider. Produces a weighted scorecard, evaluation criteria, and recommendation framework."
+---
+
+# Vendor Evaluation Skill
+
+Produces a structured vendor evaluation framework — from defining criteria through to a scored comparison and recommendation.
+
+## Required Inputs
+- **What you are procuring**
+- **Vendors being evaluated** (minimum 2)
+- **Key decision criteria** (if known)
+- **Decision makers**
+- **Budget range**
+- **Timeline to decide**
+
+## Output Structure
+
+### 1. Evaluation Criteria and Weights
+
+| Category | Weight | Rationale |
+|---|---|---|
+| Functional fit | [%] | Does it do what we need? |
+| Commercial terms | [%] | Price, flexibility, payment |
+| Implementation | [%] | How hard to get started? |
+| Support and SLA | [%] | What happens when things go wrong? |
+| Security and compliance | [%] | Meets regulatory requirements? |
+| Vendor stability | [%] | Will this company exist in 3 years? |
+| References | [%] | Who else uses this? |
+
+Weights must total 100%.
+
+### 2. Scoring Rubric
+- 5: Exceeds requirements — clear best-in-class
+- 4: Meets requirements — fully satisfies with minor gaps
+- 3: Partially meets — notable gaps requiring workarounds
+- 2: Significant gaps — would require workarounds
+- 1: Does not meet — cannot satisfy requirement
+
+### 3. Vendor Scorecard
+
+| Criterion | Weight | [Vendor A] | Weighted | [Vendor B] | Weighted | [Vendor C] | Weighted |
+|---|---|---|---|---|---|---|---|
+| Functional fit | [%] | /5 | | /5 | | /5 | |
+| [Continue...] | | | | | | | |
+| **Total** | 100% | | **/5** | | **/5** | | **/5** |
+
+### 4. Key Questions for Every Vendor
+Functional: Walk through [most critical use case]. What can your product not do that customers ask for?
+Commercial: What is included vs add-ons? Contract minimum term and notice period? Price protection at renewal?
+Implementation: Typical implementation for our size? What do you need from our team?
+Support: SLA for critical issues? Support included vs charged extra?
+Security: ISO 27001 / SOC 2 certified? Where is data stored? Breach notification process?
+
+### 5. Reference Check Questions
+- How long using [vendor]? Implementation surprises? Support responsiveness? One thing you wish you had known? Would you choose them again?
+
+### 6. Recommendation
+
+**Recommended vendor:** [Name] | **Score:** [X/5]
+**Rationale:** [Specific strengths that matter for this decision]
+**Key risks:** [Risk and mitigation]
+**Conditions:** [Contract terms to negotiate before signing]
+**Runner-up:** [Vendor and why they lost]
+
+## Example Trigger Phrases
+- "Help me evaluate vendors for [procurement]"
+- "Create a vendor scorecard for [software/service]"
+- "Compare [Vendor A] vs [Vendor B] for [use case]"