pm-claude-skills 33.0.0 → 34.0.0

package/README.md

@@ -1,4 +1,4 @@
-# 🧠 PM Skills — 378 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes
+# 🧠 PM Skills — 391 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes
 
 [![In the official Anthropic plugin directory](https://img.shields.io/badge/Anthropic%20Plugin%20Directory-Published-D97757?logo=anthropic&logoColor=white)](#-quick-install-2-minutes)
 [![Stars](https://img.shields.io/github/stars/mohitagw15856/pm-claude-skills?style=social)](https://github.com/mohitagw15856/pm-claude-skills/stargazers)
@@ -9,7 +9,7 @@
 [![MCP](https://img.shields.io/badge/MCP-registry-0098FF?logo=modelcontextprotocol&logoColor=white)](https://github.com/mohitagw15856/pm-claude-skills#-use-it-anywhere--the-ai-ecosystem)
 [![Remote MCP](https://img.shields.io/badge/ChatGPT%20%C2%B7%20Claude.ai-connector-10A37F)](mcp-remote/)
 [![Smithery](https://smithery.ai/badge/mohit15856/pm-skills)](https://smithery.ai/servers/mohit15856/pm-skills)
-[![Skills](https://img.shields.io/badge/skills-378-blue)](https://github.com/mohitagw15856/pm-claude-skills)
+[![Skills](https://img.shields.io/badge/skills-391-blue)](https://github.com/mohitagw15856/pm-claude-skills)
 [![eval](https://img.shields.io/badge/eval--scored-208%20%C2%B7%20avg%204.8%2F5-brightgreen)](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html)
 [![Subagents](https://img.shields.io/badge/subagents-4-blueviolet)](agents/)
 [![Commands](https://img.shields.io/badge/slash%20commands-19-blueviolet)](commands/)
@@ -25,7 +25,7 @@
 
 <p align="center">
   <a href="https://mohitagw15856.github.io/pm-claude-skills/">
-    <img src="https://readme-typing-svg.demolab.com?font=Inter&weight=600&size=24&pause=900&color=D97757&center=true&vCenter=true&width=720&lines=378+pro+AI+skills;PRDs%2C+roadmaps%2C+launches+%E2%80%94+done+right;Run+any+one+free+in+your+browser" alt="PM Skills" />
+    <img src="https://readme-typing-svg.demolab.com?font=Inter&weight=600&size=24&pause=900&color=D97757&center=true&vCenter=true&width=720&lines=391+pro+AI+skills;PRDs%2C+roadmaps%2C+launches+%E2%80%94+done+right;Run+any+one+free+in+your+browser" alt="PM Skills" />
   </a>
 </p>
 
@@ -56,11 +56,11 @@
 *Not sure? Start with the Playground.* This is a **CLI, not a library** — you don't need `npm install`; `npx pm-claude-skills …` always runs the latest. Browse everything first with `npx pm-claude-skills list`.
 
 > **PM stands for Professional, not just Product Management.**
-> 378 professional skills + 4 agent templates across 55 bundles covering 25 professions. Built for Claude Code — and now portable to ChatGPT, Gemini, and Hermes Agent. Built by a PM, used by everyone.
+> 391 professional skills + 4 agent templates across 56 bundles covering 25 professions. Built for Claude Code — and now portable to ChatGPT, Gemini, and Hermes Agent. Built by a PM, used by everyone.
 
 A community-built library of professional skills for every field — product management, engineering, customer success, marketing, social media, writers, design, legal, finance, HR, sales, operations, research, and more. Each skill is a structured `SKILL.md` file that teaches an AI assistant how to produce professional-grade outputs for your workflows. Skills run natively in **Claude Code** and **Hermes Agent** (same open `SKILL.md` standard), and ship as ready-to-paste exports for **ChatGPT** and **Gemini** — see [Works With](#-works-with--cross-tool-compatibility).
 
-**🆕 Latest — v33.0.0 (Personal Finance + DevRel bundles, a smarter Galaxy & ✨ Visualize):** two new bundles — **💰 `pm-money`** for individuals (budget builder, debt-payoff avalanche/snowball, investing policy statement, net-worth statement, savings-goal plan, expense audit) and **🛠️ `pm-devrel`** for shipping dev tools & OSS (Show HN/Product Hunt launch post, docs quickstart, conference CFP, changelog, README, contributor guide). New playground power: a **✨ Visualize** button adds the best-fit diagram/chart to *any* result, and several core skills (metric tree, roadmap, cohort analysis, postmortem) now emit visuals by default. And the **🌌 Galaxy** got an upgrade — star brightness now = eval score, Guided Journeys trace as glowing **constellations**, and your run history lights up as a personal trail. *Earlier (v32.0):* E-commerce, UX Writing, Recruiting & Accounting bundles. **378 skills across 55 bundles.** → **[Full release history & notes](https://github.com/mohitagw15856/pm-claude-skills/releases)**.
+**🆕 Latest — v34.0.0 (Engineering craft, a "grill me" brief-builder & marketing depth):** a new **🛠️ `pm-craft` bundle** of *how-to-work* discipline for coding agents — `tdd-workflow`, `bug-diagnosis`, `refactoring-plan`, `session-handoff`, `pr-description`, `code-review-guide` (process, not just artifacts). A new **`brief-builder`** skill that *interviews you* with sharp questions to build a tight brief before producing — the one interaction pattern the library was missing. Plus 6 marketing skills filling real gaps: `programmatic-seo`, `schema-markup`, `marketing-psychology`, `referral-program`, `co-marketing`, `paywall-optimization`. *Earlier (v33.0):* `pm-money` + `pm-devrel` bundles, the ✨ Visualize button, and the constellation Galaxy. **391 skills across 56 bundles.** → **[Full release history & notes](https://github.com/mohitagw15856/pm-claude-skills/releases)**.
 
 ### ▶ See it in action — [try the live Skill Playground](https://mohitagw15856.github.io/pm-claude-skills/)
 
@@ -89,7 +89,7 @@ A community-built library of professional skills for every field — product man
 | 🔭 [Competitor Teardown](skills/competitor-teardown) | "what are rivals up to?" | a positioning map, feature gaps & strategy |
 | 📝 [Meeting Notes](skills/meeting-notes) | a raw transcript | decisions, owners & next steps |
 
-→ Want proof first? See [**real sample outputs**](https://mohitagw15856.github.io/pm-claude-skills/examples.html) from each skill. Like what you see? [**Install in 2 minutes**](#-quick-install-2-minutes) · [browse all 378 skills](#️-all-378-skills) · [**⭐ star the repo**](https://github.com/mohitagw15856/pm-claude-skills/stargazers) so others find it.
+→ Want proof first? See [**real sample outputs**](https://mohitagw15856.github.io/pm-claude-skills/examples.html) from each skill. Like what you see? [**Install in 2 minutes**](#-quick-install-2-minutes) · [browse all 391 skills](#️-all-391-skills) · [**⭐ star the repo**](https://github.com/mohitagw15856/pm-claude-skills/stargazers) so others find it.
 
 ---
 
@@ -112,7 +112,7 @@ It's not just text — the playground exports every result as a **professionally
   </tr>
 </table>
 
-> Generate yours: run a skill in the [Playground](https://mohitagw15856.github.io/pm-claude-skills/), then **Download → PDF · Paper / Modern / Technical**. Add a `Brand color: #hex` line to your context and it tints to match (last tile). Personal documents live in the [`pm-personal`](#️-all-378-skills) bundle (résumé, cover letter, bio, LinkedIn, portfolio, one-pager).
+> Generate yours: run a skill in the [Playground](https://mohitagw15856.github.io/pm-claude-skills/), then **Download → PDF · Paper / Modern / Technical**. Add a `Brand color: #hex` line to your context and it tints to match (last tile). Personal documents live in the [`pm-personal`](#️-all-391-skills) bundle (résumé, cover letter, bio, LinkedIn, portfolio, one-pager).
 
 ---
 
@@ -121,11 +121,11 @@ It's not just text — the playground exports every result as a **professionally
 <details>
 <summary>Read more ↓</summary>
 
-The whole library on one page — install, all 378 skills by profession, the Professional Brain, the REST API, integrations, and quality tooling. Great to **print, share, or drop into a slide**.
+The whole library on one page — install, all 391 skills by profession, the Professional Brain, the REST API, integrations, and quality tooling. Great to **print, share, or drop into a slide**.
 
 <p align="center">
   <a href="CHEATSHEET.md">
-    <img src="web/docs-assets/cheatsheet.png" width="80%" alt="PM Skills one-page cheatsheet — 378 skills, the Professional Brain, REST API, integrations, and tooling at a glance." />
+    <img src="web/docs-assets/cheatsheet.png" width="80%" alt="PM Skills one-page cheatsheet — 391 skills, the Professional Brain, REST API, integrations, and tooling at a glance." />
   </a>
 </p>
 
@@ -156,7 +156,7 @@ Generic AI forgets everything between sessions, so you re-paste context forever
 <details>
 <summary>Read more ↓</summary>
 
-These 378 skills aren't a random catalog — they cover the **full arc of professional work**, end to end. Wherever you are in the loop, there's a skill for it:
+These 391 skills aren't a random catalog — they cover the **full arc of professional work**, end to end. Wherever you are in the loop, there's a skill for it:
 
 ```mermaid
 flowchart LR
@@ -175,7 +175,7 @@ flowchart LR
 | **📊 Measure** | Track outcomes & analyse | `metrics-framework` · `cohort-analysis` · `ab-test-planner` · `churn-analysis` |
 | **📣 Communicate** | Report up and out | `executive-update` · `board-deck-narrative` · `stakeholder-update` · `qbr-deck` |
 
-> New here? Start with the [**top-tier skills**](#️-skill-tiers--start-with-the-strongest), or jump straight to [**all 378 skills**](#️-all-378-skills) grouped by profession.
+> New here? Start with the [**top-tier skills**](#️-skill-tiers--start-with-the-strongest), or jump straight to [**all 391 skills**](#️-all-391-skills) grouped by profession.
 
 </details>
 
@@ -298,7 +298,7 @@ Most skill repos are a folder of prompts. This one is a **system** — measured,
 
 | | **PM Skills** | Typical skill repo |
 |---|:---:|:---:|
-| Skills | **378**, across 25 professions | a handful → dozens, usually one domain |
+| Skills | **391**, across 25 professions | a handful → dozens, usually one domain |
 | Quality | **eval-scored** on a rubric + a public [benchmark](https://mohitagw15856.github.io/pm-claude-skills/benchmark.html) | trust the README |
 | Improves itself | ✅ eval → critique → rewrite (kept only if it scores higher) | ✗ |
 | Grounded in frameworks | ✅ each cites its source (RICE, JTBD, Pyramid Principle…) | rarely |
@@ -323,13 +323,13 @@ Most skill repos are a folder of prompts. This one is a **system** — measured,
 >
 > ⚠️ **You don't need `npm install pm-claude-skills`** — it's a CLI, not a library, so there's nothing to import. Use `npx pm-claude-skills …` (it always runs the latest). `npm install` just downloads it and does nothing on its own.
 
-**With the [`skills`](https://github.com/vercel-labs/skills) CLI** (the open agent-skills installer that works across Claude Code, Cursor, Codex, OpenCode & 60+ agents) — pick from all 378 interactively:
+**With the [`skills`](https://github.com/vercel-labs/skills) CLI** (the open agent-skills installer that works across Claude Code, Cursor, Codex, OpenCode & 60+ agents) — pick from all 391 interactively:
 
 ```bash
 npx skills add mohitagw15856/pm-claude-skills            # browse & pick (auto-detects your agent)
 npx skills add mohitagw15856/pm-claude-skills --list     # just preview the catalog
 npx skills add mohitagw15856/pm-claude-skills --skill prd-template   # grab one
-npx skills add mohitagw15856/pm-claude-skills --skill '*'            # install all 378
+npx skills add mohitagw15856/pm-claude-skills --skill '*'            # install all 391
 ```
 
 **Or our own installer** — via the [`pm-claude-skills`](https://www.npmjs.com/package/pm-claude-skills) npm package (Windows/macOS/Linux, needs Node), which also installs subagents, slash commands & cross-tool exports:
@@ -338,7 +338,7 @@ npx skills add mohitagw15856/pm-claude-skills --skill '*'            # install a
 npx pm-claude-skills add --agent claude     # or: codex · cursor · hermes · openclaw
 ```
 
-**Or one-line MCP** — make all 378 skills + 5 workflow recipes available in *every* session of any MCP client (Claude Code, Claude Desktop, Cursor, Windsurf), no per-file install:
+**Or one-line MCP** — make all 391 skills + 5 workflow recipes available in *every* session of any MCP client (Claude Code, Claude Desktop, Cursor, Windsurf), no per-file install:
 
 ```bash
 claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
@@ -399,7 +399,7 @@ ln -s ~/pm-claude-skills/skills/* ~/.claude/skills/
 <details>
 <summary>Read more ↓</summary>
 
-The same 378 skills reach you through every channel — pick whatever fits your stack:
+The same 391 skills reach you through every channel — pick whatever fits your stack:
 
 | Channel | Get it |
 |---|---|
@@ -413,7 +413,7 @@ The same 378 skills reach you through every channel — pick whatever fits your
 | 🖥️ **IDE rules** | Generated exports for **Cursor, Windsurf, Aider, Cline, Continue, Zed, Roo, Kilo Code** — [`exports/`](exports/) |
 | 🤖 **Agents & answer engines** | [`llms.txt`](https://mohitagw15856.github.io/pm-claude-skills/llms.txt) makes the whole library discoverable & citable |
 
-> **208 of 378 skills are eval-scored, averaging 4.8/5** — see the [leaderboard](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html).
+> **208 of 391 skills are eval-scored, averaging 4.8/5** — see the [leaderboard](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html).
 
 > 🧠 **Give your skills memory:** the [Professional Brain](BRAIN.md) is a local markdown folder skills read, write back to, and act on. It's a folder + one file to start — **[5-minute Quickstart](BRAIN_QUICKSTART.md)**.
 
@@ -435,7 +435,7 @@ There are two kinds of support. **Native `SKILL.md` agents** read the file as-is
 auto-discover skills from the `description` frontmatter. **Other tools** take the markdown
 body as a system prompt — for those we ship ready-made [exports](#ready-to-use-exports).
 
-**In your editor (VS Code / Cursor):** the [**`vscode-extension/`**](vscode-extension/) brings all 378 skills into the Command Palette — search and *insert a skill as context* for Copilot/Cursor chat, copy it, or open it in the Playground.
+**In your editor (VS Code / Cursor):** the [**`vscode-extension/`**](vscode-extension/) brings all 391 skills into the Command Palette — search and *insert a skill as context* for Copilot/Cursor chat, copy it, or open it in the Playground.
 
 | Platform | How it works | Auto-trigger? |
 |---|---|---|
@@ -595,7 +595,7 @@ ANTHROPIC_API_KEY=sk-ant-… npx pm-claude-skills generate --from ./team-process
 
 **🏆 Skill Leaderboard — [evals](evals/).** An LLM-as-judge harness scores each skill across Claude models on structure, completeness, usefulness, and grounding. **[View the leaderboard →](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html)**
 
-> **Score the *whole* library, cheaply.** `npm run eval:gen-cases` writes a representative input for **all 378 skills** (curated cases kept verbatim; the rest auto-generated), then `npm run eval:all` runs the full pass on Haiku for **~$2** total. The weakest scorers can then be auto-rewritten with **`npm run improve -- <skill>`** (`/improve`), which keeps a change only if the score goes up.
+> **Score the *whole* library, cheaply.** `npm run eval:gen-cases` writes a representative input for **all 391 skills** (curated cases kept verbatim; the rest auto-generated), then `npm run eval:all` runs the full pass on Haiku for **~$2** total. The weakest scorers can then be auto-rewritten with **`npm run improve -- <skill>`** (`/improve`), which keeps a change only if the score goes up.
 
 </details>
 
@@ -691,7 +691,7 @@ Not sure which plugin to install? Here's what each one covers:
 
 On May 5, 2026, Anthropic [released their first agent templates](https://www.anthropic.com/news/finance-agents) — pre-packaged Claude agents that combine **skills, connectors, and subagents** into ready-to-run workflows for financial services.
 
-This library is the largest open-source collection of professional skills available — covering 20 professions beyond financial services. **The 378 skills here are the building blocks for agent templates outside of finance.**
+This library is the largest open-source collection of professional skills available — covering 20 professions beyond financial services. **The 391 skills here are the building blocks for agent templates outside of finance.**
 
 ### What is an agent template?
 
@@ -771,7 +771,7 @@ More templates will follow. If you want to contribute one, see the [template con
 <details>
 <summary>Read more ↓</summary>
 
-**Latest: v32.0.0 — 4 new bundles, 24 skills (E-commerce, UX Writing, Recruiting, Accounting).** 378 skills across 55 bundles, 25 professions. Every tagged release has complete notes on the **[Releases page](https://github.com/mohitagw15856/pm-claude-skills/releases)**.
+**Latest: v32.0.0 — 4 new bundles, 24 skills (E-commerce, UX Writing, Recruiting, Accounting).** 391 skills across 56 bundles, 25 professions. Every tagged release has complete notes on the **[Releases page](https://github.com/mohitagw15856/pm-claude-skills/releases)**.
 
 Full [Keep a Changelog](https://keepachangelog.com/)-format history — every release back to the start — is in **[CHANGELOG.md](CHANGELOG.md)**.
 
@@ -819,7 +819,7 @@ This repo was built alongside a published 16-part article series on Medium.
 <details>
 <summary>Read more ↓</summary>
 
-A 378-skill library doesn't have 378 equally-mature skills, and pretending otherwise
+A 391-skill library doesn't have 391 equally-mature skills, and pretending otherwise
 wastes your time. Skills are tiered honestly so you can start with the best work:
 
 - 🟢 **Production-Ready (50)** — battle-tested, stable output, used in real work. Includes the three skills with computed Python helpers (sprint planning, RICE, customer health). **Start here.**
@@ -834,7 +834,7 @@ If you're new, install `pm-essentials` and try a couple of Production-Ready skil
 
 ---
 
-## 🗂️ All 378 Skills
+## 🗂️ All 391 Skills
 
 <details>
 <summary>Read more ↓</summary>
@@ -867,6 +867,7 @@ Every skill, grouped by profession. **[Browse the full per-skill catalog → SKI
 | 🎨 Visuals & Diagrams | `pm-visuals` 🆕 | 11 | `flowchart` · `architecture-diagram` · `gantt-roadmap` · `chart` |
 | 💰 Personal Finance | `pm-money` 🆕 | 6 | `budget-builder` · `debt-payoff-plan` · `net-worth-statement` |
 | 🛠️ Developer Relations | `pm-devrel` 🆕 | 6 | `launch-post` · `readme-writer` · `changelog-writer` |
+| 🧑‍🔧 Engineering Craft | `pm-craft` 🆕 | 6 | `tdd-workflow` · `bug-diagnosis` · `code-review-guide` |
 
 > Full per-skill detail (folder paths, descriptions, "🆕" markers) lives in **[SKILLS.md](SKILLS.md)**.
 
@@ -879,7 +880,7 @@ Every skill, grouped by profession. **[Browse the full per-skill catalog → SKI
 <details>
 <summary>Read more ↓</summary>
 
-Building and maintaining 378 skills across 55 bundles takes real time — testing skills against new model releases, building new ones from community requests, writing the article series, and keeping documentation current.
+Building and maintaining 391 skills across 56 bundles takes real time — testing skills against new model releases, building new ones from community requests, writing the article series, and keeping documentation current.
 
 If these skills save you time at work — or you're a company that wants your logo in front of the PMs, engineers, and operators who use them daily — **[become a sponsor →](https://github.com/sponsors/mohitagw15856)** (or [☕ buy me a coffee](https://www.buymeacoffee.com/mohit15856)).
 
@@ -911,7 +912,7 @@ pull request**, and once it's merged you earn a badge to show off in your own re
 ```
 
 Community listings live in their authors' own repos and are **community-maintained — not
-eval-scored or security-audited** (that's the [curated library](#️-all-378-skills) above). Want
+eval-scored or security-audited** (that's the [curated library](#️-all-391-skills) above). Want
 your skill *in* the curated library instead? See **Contributing** below.
 
 ---

package/exports/README.md

@@ -8,7 +8,7 @@ by hand; edit the source skill and run:
 node scripts/build-exports.mjs
 ```
 
-Currently exporting **378 skills** to:
+Currently exporting **391 skills** to:
 
 - **ChatGPT — Custom GPT instructions** → `exports/chatgpt/`
 - **Google Gemini — Gem instructions** → `exports/gemini/`

package/exports/aider/README.md

@@ -3,7 +3,7 @@
 > Auto-generated from `skills/*/SKILL.md` by `scripts/build-exports.mjs`.
 > **Do not edit these files by hand** — edit the source skill and regenerate.
 
-378 skills exported. Copy a `.mdc rule` into the tool to use it.
+391 skills exported. Copy a `.mdc rule` into the tool to use it.
 
 | Skill | Bundle | Path |
 |---|---|---|
@@ -35,8 +35,10 @@
 | Bookkeeping Categorization | `pm-accounting` | `pm-accounting/bookkeeping-categorization/bookkeeping-categorization.md` |
 | Boolean Search Builder | `pm-recruiting` | `pm-recruiting/boolean-search-builder/boolean-search-builder.md` |
 | Brag Doc | `pm-career` | `pm-career/brag-doc/brag-doc.md` |
+| Brief Builder | `pm-cross` | `pm-cross/brief-builder/brief-builder.md` |
 | Budget Builder | `pm-money` | `pm-money/budget-builder/budget-builder.md` |
 | Budget Variance Analysis | `pm-finance` | `pm-finance/budget-variance-analysis/budget-variance-analysis.md` |
+| Bug Diagnosis | `pm-craft` | `pm-craft/bug-diagnosis/bug-diagnosis.md` |
 | Bug Report | `pm-qa` | `pm-qa/bug-report/bug-report.md` |
 | Candidate Scorecard | `pm-recruiting` | `pm-recruiting/candidate-scorecard/candidate-scorecard.md` |
 | Cap Table Explainer | `pm-founders` | `pm-founders/cap-table-explainer/cap-table-explainer.md` |
@@ -59,8 +61,10 @@
 | Client Discovery | `pm-consulting` | `pm-consulting/client-discovery/client-discovery.md` |
 | Clinical Case Summary | `pm-research` | `pm-research/clinical-case-summary/clinical-case-summary.md` |
 | Clinical Trial Protocol | `pm-health` | `pm-health/clinical-trial-protocol/clinical-trial-protocol.md` |
+| Co-Marketing | `pm-growth` | `pm-growth/co-marketing/co-marketing.md` |
 | Code Explainer | `pm-engineering` | `pm-engineering/code-explainer/code-explainer.md` |
 | Code Review Checklist | `pm-engineering` | `pm-engineering/code-review-checklist/code-review-checklist.md` |
+| Code Review Guide | `pm-craft` | `pm-craft/code-review-guide/code-review-guide.md` |
 | Cohort Analysis | `pm-data` | `pm-data/cohort-analysis/cohort-analysis.md` |
 | Cold Email | `pm-copy` | `pm-copy/cold-email/cold-email.md` |
 | Collections Email | `pm-accounting` | `pm-accounting/collections-email/collections-email.md` |
@@ -215,6 +219,7 @@
 | Localization Brief | `pm-localization` | `pm-localization/localization-brief/localization-brief.md` |
 | Managing Up | `pm-comms` | `pm-comms/managing-up/managing-up.md` |
 | Marketing Funnel Plan | `pm-growth` | `pm-growth/marketing-funnel-plan/marketing-funnel-plan.md` |
+| Marketing Psychology | `pm-growth` | `pm-growth/marketing-psychology/marketing-psychology.md` |
 | Marketplace Listing Optimizer | `pm-ecommerce` | `pm-ecommerce/marketplace-listing-optimizer/marketplace-listing-optimizer.md` |
 | Media Pitch | `pm-gtm` | `pm-gtm/media-pitch/media-pitch.md` |
 | Meeting Notes | `pm-essentials` | `pm-essentials/meeting-notes/meeting-notes.md` |
@@ -249,6 +254,7 @@
 | Parent Communication | `pm-education` | `pm-education/parent-communication/parent-communication.md` |
 | Partnership Proposal | `pm-sales` | `pm-sales/partnership-proposal/partnership-proposal.md` |
 | Patient Communication | `pm-research` | `pm-research/patient-communication/patient-communication.md` |
+| Paywall Optimization | `pm-growth` | `pm-growth/paywall-optimization/paywall-optimization.md` |
 | Performance Budget | `pm-engineering` | `pm-engineering/performance-budget/performance-budget.md` |
 | Performance Review | `pm-people` | `pm-people/performance-review/performance-review.md` |
 | Personal Bio | `pm-personal` | `pm-personal/personal-bio/personal-bio.md` |
@@ -257,6 +263,7 @@
 | Portfolio Page | `pm-personal` | `pm-personal/portfolio-page/portfolio-page.md` |
 | PPTX Slide Auditor | `pm-delivery` | `pm-delivery/pptx-slide-auditor/pptx-slide-auditor.md` |
 | PR Crisis Response | `pm-crisis` | `pm-crisis/pr-crisis-response/pr-crisis-response.md` |
+| PR Description | `pm-craft` | `pm-craft/pr-description/pr-description.md` |
 | PR Description Writer | `pm-engineering` | `pm-engineering/pr-description-writer/pr-description-writer.md` |
 | PRD Template | `pm-essentials` | `pm-essentials/prd-template/prd-template.md` |
 | Press Release | `pm-cross` | `pm-cross/press-release/press-release.md` |
@@ -272,6 +279,7 @@
 | Product Positioning Doc | `pm-gtm` | `pm-gtm/product-positioning-doc/product-positioning-doc.md` |
 | Professional Brain | `pm-cross` | `pm-cross/professional-brain/professional-brain.md` |
 | Professional Translator | `pm-localization` | `pm-localization/professional-translator/professional-translator.md` |
+| Programmatic SEO | `pm-growth` | `pm-growth/programmatic-seo/programmatic-seo.md` |
 | Project Status Report | `pm-operations` | `pm-operations/project-status-report/project-status-report.md` |
 | Promotion Packet | `pm-career` | `pm-career/promotion-packet/promotion-packet.md` |
 | Promotion Plan | `pm-ecommerce` | `pm-ecommerce/promotion-plan/promotion-plan.md` |
@@ -292,7 +300,9 @@
 | Recruiter Outreach | `pm-recruiting` | `pm-recruiting/recruiter-outreach/recruiter-outreach.md` |
 | Red-Team Review | `pm-cross` | `pm-cross/red-team-review/red-team-review.md` |
 | Redundancy Consultation | `pm-hr` | `pm-hr/redundancy-consultation/redundancy-consultation.md` |
+| Refactoring Plan | `pm-craft` | `pm-craft/refactoring-plan/refactoring-plan.md` |
 | Reference Letter | `pm-lifeadmin` | `pm-lifeadmin/reference-letter/reference-letter.md` |
+| Referral Program | `pm-growth` | `pm-growth/referral-program/referral-program.md` |
 | Referral Program Design | `pm-growth` | `pm-growth/referral-program-design/referral-program-design.md` |
 | Regex Builder & Explainer | `pm-engineering` | `pm-engineering/regex-builder/regex-builder.md` |
 | Regression Test Plan | `pm-qa` | `pm-qa/regression-test-plan/regression-test-plan.md` |
@@ -324,11 +334,13 @@
 | Sales Page | `pm-copy` | `pm-copy/sales-page/sales-page.md` |
 | Savings Goal Plan | `pm-money` | `pm-money/savings-goal-plan/savings-goal-plan.md` |
 | Saying No | `pm-comms` | `pm-comms/saying-no/saying-no.md` |
+| Schema Markup | `pm-growth` | `pm-growth/schema-markup/schema-markup.md` |
 | Security Threat Model | `pm-engineering` | `pm-engineering/security-threat-model/security-threat-model.md` |
 | Self-Review | `pm-career` | `pm-career/self-review/self-review.md` |
 | SEO Content Brief | `pm-gtm` | `pm-gtm/seo-content-brief/seo-content-brief.md` |
 | Sequence Diagram | `pm-visuals` | `pm-visuals/sequence-diagram/sequence-diagram.md` |
 | Service Catalog Entry | `pm-engineering` | `pm-engineering/service-catalog-entry/service-catalog-entry.md` |
+| Session Handoff | `pm-craft` | `pm-craft/session-handoff/session-handoff.md` |
 | Short-Form Script | `pm-creator` | `pm-creator/short-form-script/short-form-script.md` |
 | Skill Security Auditor | `pm-engineering` | `pm-engineering/skill-security-auditor/skill-security-auditor.md` |
 | Slide Deck | `pm-documents` | `pm-documents/slide-deck/slide-deck.md` |
@@ -359,6 +371,7 @@
 | Sycophancy Challenger | `pm-cross` | `pm-cross/sycophancy-challenger/sycophancy-challenger.md` |
 | System Design Interview | `pm-engineering` | `pm-engineering/system-design-interview/system-design-interview.md` |
 | Tax Planning Checklist | `pm-finance` | `pm-finance/tax-planning-checklist/tax-planning-checklist.md` |
+| TDD Workflow | `pm-craft` | `pm-craft/tdd-workflow/tdd-workflow.md` |
 | Teaching Lesson Plan | `pm-cross` | `pm-cross/teaching-lesson-plan/teaching-lesson-plan.md` |
 | Team Health Check | `pm-people` | `pm-people/team-health-check/team-health-check.md` |
 | Team Offsite Planner | `pm-people` | `pm-people/team-offsite-planner/team-offsite-planner.md` |

package/exports/aider/pm-craft/bug-diagnosis/bug-diagnosis.md

@@ -0,0 +1,54 @@
+# Bug Diagnosis Skill
+
+The slowest way to fix a bug is to start changing code and hope. This skill runs a disciplined diagnostic
+loop: **reproduce it reliably, isolate where it happens, hypothesize why, and test the cheapest hypothesis
+first** — narrowing until the root cause is proven, not guessed. It produces a fix *and* an explanation of why
+the bug existed.
+
+## Required Inputs
+
+Ask for these only if they aren't already provided:
+
+- **The symptom** — what's wrong: expected vs. actual behavior, error/stack trace, when it started.
+- **Repro steps** — how to trigger it (or "can't reliably reproduce yet").
+- **Context** — recent changes, environment, frequency (always / intermittent / specific inputs).
+- **What's been tried** — so we don't repeat dead ends.
+
+## Output Format
+
+### Diagnosis: [bug]
+
+**1. Reproduce** — the minimal, reliable steps to trigger it. If it's intermittent, the plan to make it deterministic (fixed input/seed, added logging, narrowed conditions). *No fixing until it reproduces.*
+
+**2. Isolate** — narrow *where* it happens: bisect (git bisect / comment-out / binary search the input), check the boundaries (what's the last known-good point vs. first bad). State the smallest scope that still shows the bug.
+
+**3. Hypotheses (ranked)** — likely causes, most-probable-and-cheapest-to-test first:
+
+| Hypothesis | Why plausible | How to test it (the cheap check) | Verdict |
+|---|---|---|---|
+
+Test them in order; record what each rules in or out.
+
+**4. Root cause** — the proven cause (not a symptom), with the evidence that confirms it.
+
+**5. Fix & guard** — the fix, **a test that fails before it and passes after** (lock the bug out), and any nearby instances of the same mistake.
+
+## Quality Checks
+
+- [ ] A reliable reproduction exists before any fix is attempted
+- [ ] The location is isolated by bisection/narrowing, not guessed
+- [ ] Hypotheses are ranked by likelihood × cheapness and tested in order
+- [ ] The stated cause is the *root* cause with evidence — not just the surface symptom
+- [ ] A regression test is added that fails before the fix and passes after
+
+## Anti-Patterns
+
+- [ ] Do not start changing code before the bug reliably reproduces
+- [ ] Do not fix the symptom and stop — trace to the underlying cause
+- [ ] Do not change several things at once — you won't know what fixed it (or hid it)
+- [ ] Do not skip the regression test — an unguarded bug comes back
+- [ ] Do not ignore "what's been tried" — re-running dead ends wastes the loop
+
+## Based On
+
+Systematic debugging method (reproduce → isolate → hypothesize → verify) — Zeller's *Why Programs Fail* / scientific-method debugging.

package/exports/aider/pm-craft/code-review-guide/code-review-guide.md

@@ -0,0 +1,59 @@
+# Code Review Guide Skill
+
+Bad code review nitpicks style while missing the design flaw, or dumps 40 ungraded comments. Good review is
+*prioritized* and *kind*: it catches what actually matters (correctness, security, design), separates blocking
+issues from nits, explains the *why*, and leaves the author better. This skill runs that review.
+
+## Required Inputs
+
+Ask for these only if they aren't already provided:
+
+- **The change** — the diff/PR, and ideally its description/intent (what it's trying to do).
+- **Context** — language/stack, conventions, the part of the system it touches, risk level.
+- **Focus** (optional) — anything specific to scrutinize (security, performance, a tricky area).
+
+## Output Format
+
+### Review: [PR / change]
+
+**Summary** — in 1–2 lines: what the change does and your overall read (solid / needs work / risky).
+
+**Review passes** — scan in priority order and note findings:
+1. **Correctness** — does it do what it claims? Edge cases, error handling, off-by-ones, concurrency.
+2. **Security & data** — input validation, authz, secrets, injection, PII handling.
+3. **Design** — is this the right approach? Coupling, the seam, simpler alternative, future pain.
+4. **Tests** — do they cover the behavior and the edges? Would they catch a regression?
+5. **Readability** — names, clarity, dead code, docs where non-obvious.
+
+**Comments (ranked by severity)** — each with file/line, the issue, *why* it matters, and a concrete suggestion:
+
+| Severity | Where | Comment & why | Suggested change |
+|---|---|---|---|
+| 🔴 Blocking | | | |
+| 🟡 Should-fix | | | |
+| 🔵 Nit / optional | | | |
+
+**What's done well** — genuinely (specific, not flattery). Reviews are also for morale and learning.
+
+**Verdict** — ✅ Approve / 🔁 Request changes / 💬 Comment — with the one or two things that gate it.
+
+## Quality Checks
+
+- [ ] Correctness, security, and design are reviewed before style — priority order
+- [ ] Comments are ranked by severity (blocking vs. should-fix vs. nit), not a flat list
+- [ ] Each comment explains *why* and offers a concrete suggestion, not just "this is wrong"
+- [ ] At least one specific thing done well is noted
+- [ ] A clear verdict (approve / request changes) with the gating issues named
+- [ ] Tone is direct but kind — critiques the code, not the author
+
+## Anti-Patterns
+
+- [ ] Do not nitpick style while missing a correctness or security problem — priority first
+- [ ] Do not dump ungraded comments — rank them so the author knows what's blocking
+- [ ] Do not say "this is wrong" without why and a suggested fix
+- [ ] Do not rewrite it your way for taste — respect working approaches; flag real issues
+- [ ] Do not be a jerk — review the code, acknowledge good work, keep the author motivated
+
+## Based On
+
+Senior code-review practice (Google's engineering review guidelines): prioritize correctness/design, severity-tag feedback, be kind.

package/exports/aider/pm-craft/pr-description/pr-description.md

@@ -0,0 +1,54 @@
+# PR Description Skill
+
+A good PR description is a gift to the reviewer: it explains *intent* before they read the diff, so review is
+fast and confident. This skill turns a change into a structured PR write-up — what and why, how it was tested,
+the risk, and where to focus — the difference between a one-pass approval and three rounds of confused
+back-and-forth.
+
+## Required Inputs
+
+Ask for these only if they aren't already provided:
+
+- **The change** — what was done (the diff summary, commits, or a description).
+- **The why** — the problem/issue it solves (link the ticket).
+- **Testing** — how it was verified (tests added, manual steps, edge cases checked).
+- **Risk & rollout** — blast radius, migrations, flags, backward compatibility, how to roll back.
+
+## Output Format
+
+### [Concise, imperative PR title] (e.g. "Add rate limiting to the login endpoint")
+
+**What & why** — 2–4 sentences: the problem and what this change does about it. Link the issue (`Closes #123`).
+
+**Changes** — the key changes as bullets (the substantive ones, not every file). Group if large.
+
+**How it was tested** — tests added/updated, and the manual verification + edge cases checked. Be specific enough that the reviewer trusts it works.
+
+**Risk & rollout** — blast radius, any migration/flag/config, backward-compatibility notes, and how to roll back if it goes wrong. Say "low risk, no migration" if so.
+
+**Reviewer guide** — where to start, what to scrutinize, anything intentionally out of scope or deferred (with a follow-up note). Call out anything you're unsure about and want eyes on.
+
+**Screenshots / output** (if UI or user-facing) — before/after.
+
+Keep it proportional — a one-line fix gets a short description; a big change earns the full structure.
+
+## Quality Checks
+
+- [ ] Title is concise and imperative; the why and linked issue are clear up front
+- [ ] Changes summarize intent, not a file-by-file dump
+- [ ] Testing is specific (what was run, which edge cases) — not "tested locally"
+- [ ] Risk, rollout, and rollback are addressed (even if "low risk, none")
+- [ ] A reviewer guide points to where to focus and flags anything uncertain
+- [ ] Length is proportional to the size of the change
+
+## Anti-Patterns
+
+- [ ] Do not just paste the commit list — explain intent the diff can't convey
+- [ ] Do not say "tested" without saying how — give the reviewer something to trust
+- [ ] Do not hide risk or migrations — surface them so they're reviewed deliberately
+- [ ] Do not write a novel for a one-line change — match effort to size
+- [ ] Do not omit the "what to focus on" — undirected review is slow review
+
+## Based On
+
+Code-review and PR best practices (explain intent, make review easy, surface risk) — modern engineering norms.

package/exports/aider/pm-craft/refactoring-plan/refactoring-plan.md

@@ -0,0 +1,55 @@
+# Refactoring Plan Skill
+
+Refactoring means improving structure **without changing behavior** — and the danger is doing it in one big
+risky sweep. This skill plans the opposite: a safety net first, then a sequence of small, behavior-preserving
+steps, each leaving the code green and committable. It separates refactoring from feature work, so you're
+never doing both at once.
+
+## Required Inputs
+
+Ask for these only if they aren't already provided:
+
+- **The code & the pain** — what's being refactored and *why* (hard to change, duplicated, slow, untestable).
+- **Test coverage** — what tests exist around it (and the framework). If none, that's step zero.
+- **The goal** — the target structure or what you want to make easy next (e.g. "so I can add payment provider #2").
+- **Constraints** — what must not change (public API, behavior, performance), time budget.
+
+## Output Format
+
+### Refactoring plan: [target]
+
+**Why & goal** — the current pain in one line, and what "better" enables.
+
+**Safety net (do first)** — the tests that must exist before touching anything. If coverage is thin, add **characterization tests** that pin current behavior (even bugs) so you'd notice any change. *Don't refactor untested code blind.*
+
+**Target structure** — a short sketch of where you're going (the shape, the seams, the names).
+
+**Steps (small & sequenced)** — each step is behavior-preserving and independently committable:
+
+| # | Step | Refactoring move | Stays green by | Commit after |
+|---|---|---|---|---|
+| 1 | … | (extract function / rename / introduce interface / move) | run tests | ✅ |
+
+Order them so risk drops early and each step is reversible.
+
+**Definition of done** — behavior identical (tests still green), the goal structure reached, no feature changes smuggled in.
+
+## Quality Checks
+
+- [ ] A safety net (existing or characterization tests) is established before any change
+- [ ] Every step is behavior-preserving and independently committable
+- [ ] Steps are small and sequenced so the code is green throughout
+- [ ] Refactoring is kept separate from behavior/feature changes
+- [ ] The target structure is explicit and tied to what it makes easier next
+
+## Anti-Patterns
+
+- [ ] Do not refactor and add features in the same commit — separate them
+- [ ] Do not start without tests — add characterization tests first if coverage is thin
+- [ ] Do not plan a big-bang rewrite — sequence small, reversible steps
+- [ ] Do not change behavior and call it refactoring — behavior must stay identical
+- [ ] Do not skip running tests between steps — that's the whole safety mechanism
+
+## Based On
+
+Refactoring discipline (Martin Fowler): behavior-preserving transformations, characterization tests, small steps.

package/exports/aider/pm-craft/session-handoff/session-handoff.md

@@ -0,0 +1,54 @@
+# Session Handoff Skill
+
+Work gets dropped at boundaries — a context window fills, a session ends, a task passes to someone else — and
+the next person (or agent) re-derives everything from scratch. This skill writes a tight **handoff** that
+carries the state across that boundary: the goal, what's done, where things stand, the exact next step, and
+the landmines. Optimised to be the first thing a fresh session reads.
+
+## Required Inputs
+
+Ask for these only if they aren't already provided (or infer from the session so far):
+
+- **The objective** — what we're ultimately trying to achieve.
+- **Progress** — what's been done and decided so far.
+- **Current state** — what's in-flight right now, what's working/broken, where files/branches are.
+- **Next step** — the single most important thing to do next.
+- **Gotchas** — dead ends tried, constraints, things that will bite the next person.
+
+## Output Format
+
+### Handoff: [task]
+
+**🎯 Objective** — the goal in 1–2 lines, and the definition of done.
+
+**✅ Done so far** — key work completed and decisions made (with the *why* for non-obvious calls), as tight bullets.
+
+**📍 Current state** — exactly where things stand: branch/PR, what runs, what's failing, files touched, any half-finished change.
+
+**⏭️ Next step** — the very next action, concrete enough to start immediately. Then the following 2–3 steps.
+
+**⚠️ Gotchas & dead ends** — what was tried and didn't work (so it isn't repeated), constraints, sharp edges, anything surprising.
+
+**🔗 Pointers** — key files (`path:line`), commands to run, links (PR, issue, docs) the next person needs.
+
+Keep it skimmable — the next reader should grasp the state in under a minute.
+
+## Quality Checks
+
+- [ ] Objective and definition-of-done are stated up front
+- [ ] Current state is concrete (branch/PR, what runs, what's broken) — not "made progress"
+- [ ] The next step is specific enough to act on immediately
+- [ ] Dead ends and gotchas are captured so they aren't repeated
+- [ ] Pointers (files, commands, links) are included; the whole thing is skimmable in ~a minute
+
+## Anti-Patterns
+
+- [ ] Do not write a vague status ("worked on the feature") — state exactly what's done and what's not
+- [ ] Do not omit dead ends — repeating failed attempts is the most common handoff waste
+- [ ] Do not bury the next step — it should be obvious and immediately actionable
+- [ ] Do not assume shared memory — the reader may have zero prior context
+- [ ] Do not pad it — a handoff nobody reads is worthless; keep it tight and scannable
+
+## Based On
+
+Engineering handoff / pairing-rotation practice and incident-handoff (SBAR-style) structure adapted for agent and human work.