You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "Structured AI workflows for better product decisions. 65 domain-specific skills and 36 chained workflows across 8 PM plugins — from discovery to strategy, execution, launch, and growth.",
4
+
"version": "2.0.0",
5
+
"description": "Structured AI workflows for better product decisions. 68 domain-specific skills and 42 chained workflows across 9 PM plugins — from discovery to strategy, execution, launch, growth, and shipping AI-built software.",
"description": "AI Shipping Kit — for PMs and founders accountable for AI-built code. Document a vibe-coded app, audit it for intended-vs-implemented security gaps and performance issues, and produce a reviewer-ready shipping packet.",
Copy file name to clipboardExpand all lines: CLAUDE.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,15 @@ Guidance for AI agents (Claude Code, Cowork, and others) working in this reposit
4
4
5
5
## Project Overview
6
6
7
-
**PM Skills** (`phuryn/pm-skills`) — a marketplace of **8 independent plugins** (65 skills, 36 commands) that bring structured product-management workflows to AI coding assistants. Built for Claude Code and Claude Cowork; the skills are also compatible with other agents (Gemini CLI, Cursor, Codex CLI).
7
+
**PM Skills** (`phuryn/pm-skills`) — a marketplace of **9 independent plugins** (68 skills, 42 commands) that bring structured product-management workflows to AI coding assistants. Built for Claude Code and Claude Cowork; the skills are also compatible with other agents (Gemini CLI, Cursor, Codex CLI).
8
8
9
9
Owner: Paweł Huryn — pawel@productcompass.pm — https://www.productcompass.pm
10
10
11
11
## Repo Structure
12
12
13
13
```
14
14
pm-skills/ <- repo root
15
-
├── .claude-plugin/marketplace.json <- root marketplace manifest (lists all 8 plugins)
15
+
├── .claude-plugin/marketplace.json <- root marketplace manifest (lists all 9 plugins)
16
16
├── .docs/images/ <- images used by README (webp, gif)
|`pm-ai-shipping`| AI Shipping Kit: document a vibe-coded app, map test coverage, audit security/performance against intended behavior, compile a shipping packet |
44
45
45
46
## Key Design Rules
46
47
@@ -68,9 +69,9 @@ Descriptions in `plugin.json` and the repo `README.md` should stay aligned (iden
68
69
69
70
## Versioning
70
71
71
-
- All versions are currently **1.0.1** — `marketplace.json` and all 8`plugin.json` files.
72
+
- All versions are currently **2.0.0** — `marketplace.json` and all 9`plugin.json` files.
72
73
-**Keep every version in sync.** There is no independent per-plugin versioning.
73
-
- Bump any `plugin.json` → also bump `marketplace.json`, and vice-versa (bump all 8 to match).
74
+
- Bump any `plugin.json` → also bump `marketplace.json`, and vice-versa (bump all 9 to match).
Copy file name to clipboardExpand all lines: README.md
+44-7Lines changed: 44 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,9 @@
5
5
6
6
# PM Skills Marketplace: The AI Operating System for Better Product Decisions
7
7
8
-
> 65 PM skills and 36 chained workflows across 8 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, and growth.
8
+
> 68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code.

11
11
12
12
Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
13
13
@@ -31,13 +31,15 @@ The result: better product decisions, not just faster documents.
31
31
32
32
## How It Works (Skills, Commands, Plugins)
33
33
34
+

35
+
34
36
**Skills** are the building blocks of the marketplace. Each skill gives Claude domain knowledge, analytical frameworks, or a guided workflow for a specific PM task. Some skills also work as reusable foundations that multiple commands share.
35
37
36
38
Skills are loaded automatically when relevant to the conversation — no explicit invocation needed. If needed (e.g., prioritizing skills over general knowledge), you can **force loading skills** with `/plugin-name:skill-name` or `/skill-name` (Claude will add the prefix).
37
39
38
40
**Commands** are user-triggered workflows invoked with `/command-name`. They chain one or more skills into an end-to-end process. For example, `/discover` chains four skills together: brainstorm-ideas → identify-assumptions → prioritize-assumptions → brainstorm-experiments.
39
41
40
-
**Plugins** group related skills and commands into installable packages. Each plugin covers a PM domain — discovery, strategy, execution, and so on. Installing the marketplace gives you all 8 plugins at once.
42
+
**Plugins** group related skills and commands into installable packages. Each plugin covers a PM domain — discovery, strategy, execution, and so on. Installing the marketplace gives you all 9 plugins at once.
-`strategy-red-team` — Adversarial stress-test of a plan: surface load-bearing assumptions, name what would make each one fail, and rank by cheapest test
212
216
213
-
**Commands (10):**
217
+
**Commands (11):**
214
218
215
219
-`/write-prd` — Create a PRD from a feature idea or problem statement
216
220
-`/plan-okrs` — Brainstorm team-level OKRs
217
221
-`/transform-roadmap` — Convert a feature-based roadmap into outcome-focused
-`/pre-mortem` — Pre-mortem risk analysis on a PRD or launch plan
224
+
-`/red-team-prd` — Adversarially stress-test a PRD, roadmap, or strategy and rank the riskiest assumptions by cheapest test
220
225
-`/meeting-notes` — Summarize a meeting transcript into structured notes
221
226
-`/stakeholder-map` — Map stakeholders and create a communication plan
222
227
-`/write-stories` — Break features into backlog items (`user|job|wwa`)
@@ -400,6 +405,38 @@ Commands:
400
405
401
406
</details>
402
407
408
+
<details>
409
+
<summary><strong>9. pm-ai-shipping</strong> — AI Shipping Kit: document a vibe-coded app, audit security and performance, map test coverage, compile a shipping packet (2 skills, 5 commands)</summary>
410
+
411
+
For PMs and founders accountable for AI-built code. AI agents write code fast but leave no record of *intent* — what the system should do, who may do what, where the secrets live, which rules are actually verified. This kit restores reviewability: it documents the system, then audits the gap between what the docs say and what the code actually does — the class of bug generic scanners miss.
412
+
413
+
**Skills (2):**
414
+
415
+
-`shipping-artifacts` — The durable documentation set that makes an AI-built app reviewable: a core every app needs (architecture, user/permission flows, permissions, variables/secrets, test-coverage map) plus conditional docs added only when they apply (emails, cron, SEO, embedded agents/automation). Defines what each doc must capture and how a reviewer uses it
416
+
-`intended-vs-implemented` — The method for finding the gap between what a system is documented to do and what the code actually does, with cited evidence on both sides
417
+
418
+
**Commands (5):**
419
+
420
+
-`/ship-check` — Turn a vibe-coded repo into a reviewer-ready shipping packet: document, wire agent context, run security and performance audits, map test coverage, and compile the results
421
+
-`/document-app` — Reverse-engineer a codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply
422
+
-`/derive-tests` — Turn documented intent into a test-coverage map: inventory the tests that exist today, separate them from proposed tests and unverified gaps, and recommend a green-before-merge CI gate
423
+
-`/security-audit-static` — Static security audit: map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks
424
+
-`/performance-audit-static` — Static performance audit: find over-fetching, missing indexes, and caching opportunities, ranked by effort and impact
425
+
426
+
**Examples:**
427
+
428
+
Skills:
429
+
-`What documentation does my Supabase app need before someone can review it?`
430
+
-`Where does what this code does diverge from what the docs say it should do?`
431
+
432
+
Commands:
433
+
-`/ship-check the payments service`
434
+
-`/document-app — Reverse-engineer the system docs for this repo`
435
+
-`/derive-tests — Which documented rules have no test yet?`
"description": "AI Shipping Kit — for PMs and founders accountable for AI-built code. Document a vibe-coded app, audit it for intended-vs-implemented security gaps and performance issues, and produce a reviewer-ready shipping packet.",
For PMs and founders accountable for AI-built code. Document a vibe-coded app, audit it for intended-vs-implemented security gaps and performance issues, and produce a reviewer-ready shipping packet.
4
+
5
+
## Overview
6
+
7
+
AI agents write code fast but leave no record of *intent* — what the system should do, who may do what, where the secrets live. Without that record, no human and no auditing agent can tell whether the code is safe to ship. This kit restores reviewability: it documents the system, then audits the gap between what the docs say and what the code does — the class of bug generic scanners miss because they have no model of intent.
8
+
9
+
Start with `/ship-check` for the full sequence, or run a single stage with the specialist commands.
10
+
11
+
## Install
12
+
13
+
Install from the [pm-skills marketplace](https://github.com/phuryn/pm-skills) and enable the `pm-ai-shipping` plugin. Each command can be triggered with `/pm-ai-shipping:<command>` or its short `/<command>` form; skills auto-load when the topic matches.
14
+
15
+
## Skills (2)
16
+
17
+
-**shipping-artifacts** — The durable documentation set that makes an AI-built app reviewable: a core every app needs (architecture, user/permission flows, permissions, variables/secrets, test-coverage map) plus conditional docs added only when they apply (emails, cron, SEO, embedded agents/automation). Defines what each doc must capture and how a reviewer uses it.
18
+
-**intended-vs-implemented** — The method for finding the gap between what a system is documented to do and what the code actually does, with cited evidence on both sides and without hand-wavy findings.
19
+
20
+
## Commands (5)
21
+
22
+
-`/pm-ai-shipping:ship-check` — Turn a vibe-coded repo into a reviewer-ready shipping packet: document, wire agent context, run security and performance audits, map test coverage, and compile the results.
23
+
-`/pm-ai-shipping:document-app` — Reverse-engineer a codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
24
+
-`/pm-ai-shipping:derive-tests` — Turn documented intent into a test-coverage map: inventory the tests that exist today, separate them from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI gate.
25
+
-`/pm-ai-shipping:security-audit-static` — Static security audit: map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
26
+
-`/pm-ai-shipping:performance-audit-static` — Static performance audit: find over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
27
+
28
+
## Author
29
+
30
+
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
0 commit comments