Skip to content
Back to search

pm-skills

SkillWorks with CodexGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/deanpeters-product-manager-skills/badge.svg)](/listings/deanpeters-product-manager-skills)

HTML

<a href="/listings/deanpeters-product-manager-skills"><img src="/api/listings/deanpeters-product-manager-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 1,376 lines
  1. {
  2. "name": "pm-skills",
  3. "owner": {
  4. "name": "Dean Peters",
  5. "email": "dean.peters@productside.com"
  6. },
  7. "metadata": {
  8. "description": "95 battle-tested product management skills for Claude Code \u2014 discovery, strategy, finance, career, lifecycle, and more.",
  9. "version": "0.86.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "product-manager-skills",
  14. "source": "./",
  15. "description": "All PM skills in one install \u2014 discovery, strategy, delivery, finance, career, lifecycle, and more. Choose this OR individual skills, not both.",
  16. "category": "bundle",
  17. "tags": [
  18. "pm",
  19. "bundle",
  20. "all-skills"
  21. ],
  22. "strict": false
  23. },
  24. {
  25. "name": "pm-determine",
  26. "source": "./plugins/pm-determine",
  27. "description": "Set outcomes and read the terrain: strategy, finance, market, customers. 24 skills (Direct, Diagnose, Detect, Describe); shared helper skills included.",
  28. "category": "lifecycle-bundle",
  29. "tags": [
  30. "pm",
  31. "bundle",
  32. "determine",
  33. "direct",
  34. "diagnose",
  35. "detect",
  36. "describe"
  37. ]
  38. },
  39. {
  40. "name": "pm-discover",
  41. "source": "./plugins/pm-discover",
  42. "description": "Find and frame the real problem. 12 skills (Drill-down, Dig, Decode); shared helper skills included.",
  43. "category": "lifecycle-bundle",
  44. "tags": [
  45. "pm",
  46. "bundle",
  47. "discover",
  48. "drill-down",
  49. "dig",
  50. "decode"
  51. ]
  52. },
  53. {
  54. "name": "pm-define",
  55. "source": "./plugins/pm-define",
  56. "description": "Shape a solution worth building and test the bet. 9 skills (De-risk, Differentiate); shared helper skills included.",
  57. "category": "lifecycle-bundle",
  58. "tags": [
  59. "pm",
  60. "bundle",
  61. "define",
  62. "de-risk",
  63. "differentiate"
  64. ]
  65. },
  66. {
  67. "name": "pm-develop",
  68. "source": "./plugins/pm-develop",
  69. "description": "Turn the chosen solution into buildable work. 16 skills (Document, Draft, Decide, Delegate, Drumbeat); shared helper skills included.",
  70. "category": "lifecycle-bundle",
  71. "tags": [
  72. "pm",
  73. "bundle",
  74. "develop",
  75. "document",
  76. "draft",
  77. "decide",
  78. "delegate",
  79. "drumbeat"
  80. ]
  81. },
  82. {
  83. "name": "pm-deliver",
  84. "source": "./plugins/pm-deliver",
  85. "description": "Take it to market, measure it, and retire it well. 18 skills (Debut, Dollars, Demand, Dashboard, Deepen, Decommission); shared helper skills included.",
  86. "category": "lifecycle-bundle",
  87. "tags": [
  88. "pm",
  89. "bundle",
  90. "deliver",
  91. "debut",
  92. "dollars",
  93. "demand",
  94. "dashboard",
  95. "deepen",
  96. "decommission"
  97. ]
  98. },
  99. {
  100. "name": "pm-drive",
  101. "source": "./plugins/pm-drive",
  102. "description": "Drive your career and your stakeholders. 11 skills (Diplomacy, Demystify, Delineate); shared helper skills included.",
  103. "category": "lifecycle-bundle",
  104. "tags": [
  105. "pm",
  106. "bundle",
  107. "drive",
  108. "diplomacy",
  109. "demystify",
  110. "delineate"
  111. ]
  112. },
  113. {
  114. "name": "acquisition-channel-advisor",
  115. "source": "./skills/acquisition-channel-advisor",
  116. "description": "Evaluate acquisition channels using unit economics, customer quality, and scalability.",
  117. "category": "finance",
  118. "tags": [
  119. "pm",
  120. "finance",
  121. "acquisition",
  122. "unit-economics",
  123. "growth"
  124. ],
  125. "strict": false
  126. },
  127. {
  128. "name": "agent-orchestration-advisor",
  129. "source": "./skills/agent-orchestration-advisor",
  130. "description": "Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring.",
  131. "category": "ai",
  132. "tags": [
  133. "pm",
  134. "ai",
  135. "agents",
  136. "orchestration",
  137. "workflows"
  138. ],
  139. "strict": false
  140. },
  141. {
  142. "name": "ai-shaped-readiness-advisor",
  143. "source": "./skills/ai-shaped-readiness-advisor",
  144. "description": "Assess whether your product work is AI-first or AI-shaped across 5 competencies.",
  145. "category": "ai",
  146. "tags": [
  147. "pm",
  148. "ai",
  149. "readiness",
  150. "assessment",
  151. "competencies"
  152. ],
  153. "strict": false
  154. },
  155. {
  156. "name": "altitude-horizon-framework",
  157. "source": "./skills/altitude-horizon-framework",
  158. "description": "Understand the PM-to-Director transition through altitude and horizon thinking.",
  159. "category": "career",
  160. "tags": [
  161. "pm",
  162. "career",
  163. "director",
  164. "leadership",
  165. "transition"
  166. ],
  167. "strict": false
  168. },
  169. {
  170. "name": "ansoff-matrix",
  171. "source": "./skills/ansoff-matrix",
  172. "description": "Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing.",
  173. "category": "market-intelligence",
  174. "tags": [
  175. "pm",
  176. "market-intelligence",
  177. "growth",
  178. "strategy",
  179. "ansoff"
  180. ],
  181. "strict": false
  182. },
  183. {
  184. "name": "autonomous-investigation",
  185. "source": "./skills/autonomous-investigation",
  186. "description": "Protocol for AI research that proceeds without you: evidence labels, search-plan gate, diffable output.",
  187. "category": "market-intelligence",
  188. "tags": [
  189. "pm",
  190. "market-intelligence",
  191. "research",
  192. "protocol",
  193. "evidence"
  194. ],
  195. "strict": false
  196. },
  197. {
  198. "name": "battle-card-builder",
  199. "source": "./skills/battle-card-builder",
  200. "description": "Research and draft a competitive battle card from public evidence, every claim labeled and sourced.",
  201. "category": "market-intelligence",
  202. "tags": [
  203. "pm",
  204. "market-intelligence",
  205. "competitive",
  206. "sales-enablement",
  207. "battle-card"
  208. ],
  209. "strict": false
  210. },
  211. {
  212. "name": "business-health-diagnostic",
  213. "source": "./skills/business-health-diagnostic",
  214. "description": "Diagnose SaaS business health across growth, retention, efficiency, and capital.",
  215. "category": "finance",
  216. "tags": [
  217. "pm",
  218. "finance",
  219. "saas",
  220. "metrics",
  221. "diagnostic"
  222. ],
  223. "strict": false
  224. },
  225. {
  226. "name": "company-intel",
  227. "source": "./skills/company-intel",
  228. "description": "Research a company, industry, or competitor set using web search and seven analytical lenses.",
  229. "category": "discovery",
  230. "tags": [
  231. "pm",
  232. "research",
  233. "competitive-analysis",
  234. "market-intel"
  235. ],
  236. "strict": false
  237. },
  238. {
  239. "name": "company-research",
  240. "source": "./skills/company-research",
  241. "description": "Create a company research brief with executive quotes, product strategy, and org context.",
  242. "category": "discovery",
  243. "tags": [
  244. "pm",
  245. "research",
  246. "competitive-analysis",
  247. "interviews"
  248. ],
  249. "strict": false
  250. },
  251. {
  252. "name": "competitive-analysis-process",
  253. "source": "./skills/competitive-analysis-process",
  254. "description": "Orchestrate a complete six-step competitive analysis, from landscape overview to strategic direction.",
  255. "category": "market-intelligence",
  256. "tags": [
  257. "pm",
  258. "market-intelligence",
  259. "competitive",
  260. "process",
  261. "orchestration"
  262. ],
  263. "strict": false
  264. },
  265. {
  266. "name": "competitive-intel-watch",
  267. "source": "./skills/competitive-intel-watch",
  268. "description": "Scheduled delta monitor for competitive shifts: material changes only, with battle-card update flags.",
  269. "category": "market-intelligence",
  270. "tags": [
  271. "pm",
  272. "market-intelligence",
  273. "competitive",
  274. "monitoring",
  275. "delta"
  276. ],
  277. "strict": false
  278. },
  279. {
  280. "name": "competitive-research-snapshot",
  281. "source": "./skills/competitive-research-snapshot",
  282. "description": "Cited competitive landscape research with comparison matrix and so-what implications.",
  283. "category": "market-intelligence",
  284. "tags": [
  285. "pm",
  286. "market-intelligence",
  287. "competitive",
  288. "research",
  289. "citations"
  290. ],
  291. "strict": false
  292. },
  293. {
  294. "name": "context-engineering-advisor",
  295. "source": "./skills/context-engineering-advisor",
  296. "description": "Diagnose context stuffing vs. context engineering in AI workflows.",
  297. "category": "ai",
  298. "tags": [
  299. "pm",
  300. "ai",
  301. "context-engineering",
  302. "llm",
  303. "prompting"
  304. ],
  305. "strict": false
  306. },
  307. {
  308. "name": "customer-journey-map",
  309. "source": "./skills/customer-journey-map",
  310. "description": "Create a customer journey map across stages, touchpoints, actions, emotions, and metrics.",
  311. "category": "discovery",
  312. "tags": [
  313. "pm",
  314. "journey-map",
  315. "ux",
  316. "customer-experience"
  317. ],
  318. "strict": false
  319. },
  320. {
  321. "name": "customer-journey-mapping-workshop",
  322. "source": "./skills/customer-journey-mapping-workshop",
  323. "description": "Run a customer journey mapping workshop with adaptive questions and outputs.",
  324. "category": "discovery",
  325. "tags": [
  326. "pm",
  327. "journey-map",
  328. "workshop",
  329. "facilitation"
  330. ],
  331. "strict": false
  332. },
  333. {
  334. "name": "derisk-measurement-advisor",
  335. "source": "./skills/derisk-measurement-advisor",
  336. "description": "Identify what to measure, test, or track to de-risk a product or AI idea.",
  337. "category": "strategy",
  338. "tags": [
  339. "pm",
  340. "risk",
  341. "validation",
  342. "metrics"
  343. ],
  344. "strict": false
  345. },
  346. {
  347. "name": "director-readiness-advisor",
  348. "source": "./skills/director-readiness-advisor",
  349. "description": "Guide the PM-to-Director transition across preparing, interviewing, and landing.",
  350. "category": "career",
  351. "tags": [
  352. "pm",
  353. "career",
  354. "director",
  355. "coaching",
  356. "transition"
  357. ],
  358. "strict": false
  359. },
  360. {
  361. "name": "discovery-interview-prep",
  362. "source": "./skills/discovery-interview-prep",
  363. "description": "Plan customer discovery interviews with the right goal, segment, constraints, and method.",
  364. "category": "discovery",
  365. "tags": [
  366. "pm",
  367. "discovery",
  368. "interviews",
  369. "customer-research"
  370. ],
  371. "strict": false
  372. },
  373. {
  374. "name": "discovery-process",
  375. "source": "./skills/discovery-process",
  376. "description": "Run a full discovery cycle from problem hypothesis to validated solution.",
  377. "category": "discovery",
  378. "tags": [
  379. "pm",
  380. "discovery",
  381. "validation",
  382. "workflow"
  383. ],
  384. "strict": false
  385. },
  386. {
  387. "name": "eol-checklist",
  388. "source": "./skills/eol-checklist",
  389. "description": "Build a phase-gated EOL checklist sized to the sunset, with an owner per item.",
  390. "category": "strategy",
  391. "tags": [
  392. "pm",
  393. "eol",
  394. "sunset",
  395. "planning"
  396. ],
  397. "strict": false
  398. },
  399. {
  400. "name": "eol-internal-enablement",
  401. "source": "./skills/eol-internal-enablement",
  402. "description": "Build the support FAQ, sales talking points, and objection handling before an EOL.",
  403. "category": "strategy",
  404. "tags": [
  405. "pm",
  406. "eol",
  407. "enablement",
  408. "sunset"
  409. ],
  410. "strict": false
  411. },
  412. {
  413. "name": "eol-message",
  414. "source": "./skills/eol-message",
  415. "description": "Write a right-sized EOL announcement with rationale, impact, and next steps.",
  416. "category": "strategy",
  417. "tags": [
  418. "pm",
  419. "eol",
  420. "communication",
  421. "sunset"
  422. ],
  423. "strict": false
  424. },
  425. {
  426. "name": "eol-process",
  427. "source": "./skills/eol-process",
  428. "description": "Run a product sunset end to end: decide, align, plan, prepare, announce, close.",
  429. "category": "strategy",
  430. "tags": [
  431. "pm",
  432. "eol",
  433. "sunset",
  434. "workflow"
  435. ],
  436. "strict": false
  437. },
  438. {
  439. "name": "eol-readiness-advisor",
  440. "source": "./skills/eol-readiness-advisor",
  441. "description": "Run a go/no-go assessment for retiring a product, then right-size the effort.",
  442. "category": "strategy",
  443. "tags": [
  444. "pm",
  445. "eol",
  446. "sunset",
  447. "decision"
  448. ],
  449. "strict": false
  450. },
  451. {
  452. "name": "eol-stakeholder-sequence",
  453. "source": "./skills/eol-stakeholder-sequence",
  454. "description": "Plan who to talk to about a sunset, in what order, and what each must cover.",
  455. "category": "strategy",
  456. "tags": [
  457. "pm",
  458. "eol",
  459. "stakeholders",
  460. "sunset"
  461. ],
  462. "strict": false
  463. },
  464. {
  465. "name": "epic-breakdown-advisor",
  466. "source": "./skills/epic-breakdown-advisor",
  467. "description": "Break down epics into user stories with Humanizing Work split patterns.",
  468. "category": "delivery",
  469. "tags": [
  470. "pm",
  471. "epics",
  472. "splitting",
  473. "backlog"
  474. ],
  475. "strict": false
  476. },
  477. {
  478. "name": "epic-hypothesis",
  479. "source": "./skills/epic-hypothesis",
  480. "description": "Frame an epic as a testable hypothesis with target user, outcome, and validation.",
  481. "category": "delivery",
  482. "tags": [
  483. "pm",
  484. "epics",
  485. "hypothesis",
  486. "validation"
  487. ],
  488. "strict": false
  489. },
  490. {
  491. "name": "executive-onboarding-playbook",
  492. "source": "./skills/executive-onboarding-playbook",
  493. "description": "Plan a VP or CPO 30-60-90 day diagnostic onboarding path.",
  494. "category": "career",
  495. "tags": [
  496. "pm",
  497. "career",
  498. "executive",
  499. "onboarding",
  500. "vp",
  501. "cpo"
  502. ],
  503. "strict": false
  504. },
  505. {
  506. "name": "feature-investment-advisor",
  507. "source": "./skills/feature-investment-advisor",
  508. "description": "Evaluate feature investments using revenue impact, cost structure, ROI, and strategy.",
  509. "category": "finance",
  510. "tags": [
  511. "pm",
  512. "finance",
  513. "roi",
  514. "investment",
  515. "feature"
  516. ],
  517. "strict": false
  518. },
  519. {
  520. "name": "finance-based-pricing-advisor",
  521. "source": "./skills/finance-based-pricing-advisor",
  522. "description": "Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback.",
  523. "category": "finance",
  524. "tags": [
  525. "pm",
  526. "finance",
  527. "pricing",
  528. "arpu",
  529. "churn"
  530. ],
  531. "strict": false
  532. },
  533. {
  534. "name": "finance-metrics-quickref",
  535. "source": "./skills/finance-metrics-quickref",
  536. "description": "Look up SaaS finance metrics, formulas, and benchmarks fast.",
  537. "category": "finance",
  538. "tags": [
  539. "pm",
  540. "finance",
  541. "metrics",
  542. "reference",
  543. "saas"
  544. ],
  545. "strict": false
  546. },
  547. {
  548. "name": "incoming-request-advisor",
  549. "source": "./skills/incoming-request-advisor",
  550. "description": "Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done.",
  551. "category": "stakeholder",
  552. "tags": [
  553. "pm",
  554. "stakeholder",
  555. "communication",
  556. "triage",
  557. "jobs-to-be-done"
  558. ],
  559. "strict": false
  560. },
  561. {
  562. "name": "intel-discipline-advisor",
  563. "source": "./skills/intel-discipline-advisor",
  564. "description": "Triage a competitive question into the right intelligence disciplines, cadence, and executing skill.",
  565. "category": "market-intelligence",
  566. "tags": [
  567. "pm",
  568. "market-intelligence",
  569. "advisor",
  570. "triage",
  571. "research"
  572. ],
  573. "strict": false
  574. },
  575. {
  576. "name": "intelligence-collection-disciplines",
  577. "source": "./skills/intelligence-collection-disciplines",
  578. "description": "Eight intelligence-community collection disciplines for PMs, with sources, signal chains, and fusion.",
  579. "category": "market-intelligence",
  580. "tags": [
  581. "pm",
  582. "market-intelligence",
  583. "osint",
  584. "research",
  585. "fusion"
  586. ],
  587. "strict": false
  588. },
  589. {
  590. "name": "jobs-to-be-done",
  591. "source": "./skills/jobs-to-be-done",
  592. "description": "Uncover customer jobs, pains, and gains in a structured JTBD format.",
  593. "category": "discovery",
  594. "tags": [
  595. "pm",
  596. "jtbd",
  597. "customer-needs",
  598. "discovery"
  599. ],
  600. "strict": false
  601. },
  602. {
  603. "name": "lean-ux-canvas",
  604. "source": "./skills/lean-ux-canvas",
  605. "description": "Guide teams through Lean UX Canvas v2 to frame problems and surface assumptions.",
  606. "category": "discovery",
  607. "tags": [
  608. "pm",
  609. "lean-ux",
  610. "assumptions",
  611. "experimentation"
  612. ],
  613. "strict": false
  614. },
  615. {
  616. "name": "lifecycle-play-advisor",
  617. "source": "./skills/lifecycle-play-advisor",
  618. "description": "Diagnose a product's lifecycle stage and pick the play: extend, replace, or retire.",
  619. "category": "strategy",
  620. "tags": [
  621. "pm",
  622. "lifecycle",
  623. "strategy",
  624. "decision"
  625. ],
  626. "strict": false
  627. },
  628. {
  629. "name": "market-landscape-scan",
  630. "source": "./skills/market-landscape-scan",
  631. "description": "Map a market's segments, players, substitutes, and whitespace with cited evidence before sizing or positioning.",
  632. "category": "market-intelligence",
  633. "tags": [
  634. "pm",
  635. "market-intelligence",
  636. "market-research",
  637. "segmentation",
  638. "whitespace"
  639. ],
  640. "strict": false
  641. },
  642. {
  643. "name": "opportunity-solution-tree",
  644. "source": "./skills/opportunity-solution-tree",
  645. "description": "Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests.",
  646. "category": "discovery",
  647. "tags": [
  648. "pm",
  649. "ost",
  650. "teresa-torres",
  651. "continuous-discovery"
  652. ],
  653. "strict": false
  654. },
  655. {
  656. "name": "organic-growth-advisor",
  657. "source": "./skills/organic-growth-advisor",
  658. "description": "Identify which organic growth path to pursue \u2014 new segments, geographies, channels, or products.",
  659. "category": "strategy",
  660. "tags": [
  661. "pm",
  662. "growth",
  663. "strategy",
  664. "market-expansion"
  665. ],
  666. "strict": false
  667. },
  668. {
  669. "name": "pestel-analysis",
  670. "source": "./skills/pestel-analysis",
  671. "description": "Analyze political, economic, social, technological, environmental, and legal forces.",
  672. "category": "strategy",
  673. "tags": [
  674. "pm",
  675. "pestel",
  676. "macro-environment",
  677. "strategy"
  678. ],
  679. "strict": false
  680. },
  681. {
  682. "name": "pestel-delta-monitor",
  683. "source": "./skills/pestel-delta-monitor",
  684. "description": "Quarterly PESTEL re-scan: which macro factors moved, which assumptions broke, what's new to the frame.",
  685. "category": "market-intelligence",
  686. "tags": [
  687. "pm",
  688. "market-intelligence",
  689. "pestel",
  690. "monitoring",
  691. "macro"
  692. ],
  693. "strict": false
  694. },
  695. {
  696. "name": "pm-skills-navigator",
  697. "source": "./skills/pm-skills-navigator",
  698. "description": "Find the right PM skill for the situation on your desk, by lifecycle phase.",
  699. "category": "meta",
  700. "tags": [
  701. "pm",
  702. "navigation",
  703. "lifecycle",
  704. "meta"
  705. ],
  706. "strict": false
  707. },
  708. {
  709. "name": "pm-skill-creator",
  710. "source": "./skills/pm-skill-creator",
  711. "description": "Design a new PM skill through guided conversation.",
  712. "category": "meta",
  713. "tags": [
  714. "pm",
  715. "skill-authoring",
  716. "meta"
  717. ],
  718. "strict": false
  719. },
  720. {
  721. "name": "pol-probe",
  722. "source": "./skills/pol-probe",
  723. "description": "Define a Proof of Life probe to test a risky hypothesis cheaply.",
  724. "category": "ai",
  725. "tags": [
  726. "pm",
  727. "validation",
  728. "proof-of-life",
  729. "experimentation"
  730. ],
  731. "strict": false
  732. },
  733. {
  734. "name": "pol-probe-advisor",
  735. "source": "./skills/pol-probe-advisor",
  736. "description": "Select the right Proof of Life probe type based on hypothesis, risk, and resources.",
  737. "category": "ai",
  738. "tags": [
  739. "pm",
  740. "validation",
  741. "proof-of-life",
  742. "advisor"
  743. ],
  744. "strict": false
  745. },
  746. {
  747. "name": "porters-five-forces",
  748. "source": "./skills/porters-five-forces",
  749. "description": "Read an industry's structure through Porter's Five Forces with documented signals and the profit-pool close.",
  750. "category": "market-intelligence",
  751. "tags": [
  752. "pm",
  753. "market-intelligence",
  754. "strategy",
  755. "porter",
  756. "industry"
  757. ],
  758. "strict": false
  759. },
  760. {
  761. "name": "positioning-statement",
  762. "source": "./skills/positioning-statement",
  763. "description": "Create a Geoffrey Moore-style positioning statement for your product.",
  764. "category": "strategy",
  765. "tags": [
  766. "pm",
  767. "positioning",
  768. "geoffrey-moore",
  769. "messaging"
  770. ],
  771. "strict": false
  772. },
  773. {
  774. "name": "positioning-workshop",
  775. "source": "./skills/positioning-workshop",
  776. "description": "Run a positioning workshop to surface target customer, need, category, and differentiation.",
  777. "category": "strategy",
  778. "tags": [
  779. "pm",
  780. "positioning",
  781. "workshop",
  782. "messaging"
  783. ],
  784. "strict": false
  785. },
  786. {
  787. "name": "prd-development",
  788. "source": "./skills/prd-development",
  789. "description": "Build a structured PRD connecting problem, users, solution, and success criteria.",
  790. "category": "strategy",
  791. "tags": [
  792. "pm",
  793. "prd",
  794. "requirements",
  795. "workflow"
  796. ],
  797. "strict": false
  798. },
  799. {
  800. "name": "press-release",
  801. "source": "./skills/press-release",
  802. "description": "Write an Amazon-style press release that defines customer value before building.",
  803. "category": "strategy",
  804. "tags": [
  805. "pm",
  806. "press-release",
  807. "amazon",
  808. "working-backwards"
  809. ],
  810. "strict": false
  811. },
  812. {
  813. "name": "launch-plan",
  814. "source": "./skills/launch-plan",
  815. "description": "Build a tiered launch plan with owners, go/no-go criteria, and a readiness scorecard.",
  816. "category": "strategy",
  817. "tags": [
  818. "pm",
  819. "launch",
  820. "go-to-market",
  821. "workflow"
  822. ],
  823. "strict": false
  824. },
  825. {
  826. "name": "launch-metrics",
  827. "source": "./skills/launch-metrics",
  828. "description": "Define launch success metrics, decision triggers, and 30/90/180-day reviews before you launch.",
  829. "category": "strategy",
  830. "tags": [
  831. "pm",
  832. "launch",
  833. "metrics",
  834. "component"
  835. ],
  836. "strict": false
  837. },
  838. {
  839. "name": "message-house",
  840. "source": "./skills/message-house",
  841. "description": "Build a message house: one roof message, value pillars, sourced proof, and role and channel variants.",
  842. "category": "strategy",
  843. "tags": [
  844. "pm",
  845. "launch",
  846. "go-to-market",
  847. "component",
  848. "messaging"
  849. ],
  850. "strict": false
  851. },
  852. {
  853. "name": "sales-value-narrative",
  854. "source": "./skills/sales-value-narrative",
  855. "description": "Build a sales story: why change, why now, why us, value by role, objections, do-not-say.",
  856. "category": "strategy",
  857. "tags": [
  858. "pm",
  859. "launch",
  860. "go-to-market",
  861. "component",
  862. "sales"
  863. ],
  864. "strict": false
  865. },
  866. {
  867. "name": "buying-journey-enablement",
  868. "source": "./skills/buying-journey-enablement",
  869. "description": "Map how buyers buy and assign the enablement asset for each stage, role, and channel.",
  870. "category": "strategy",
  871. "tags": [
  872. "pm",
  873. "launch",
  874. "go-to-market",
  875. "workflow",
  876. "enablement"
  877. ],
  878. "strict": false
  879. },
  880. {
  881. "name": "research-synthesis",
  882. "source": "./skills/research-synthesis",
  883. "description": "Turn raw interview notes and feedback into themes, insights, and opportunity statements.",
  884. "category": "discovery",
  885. "tags": [
  886. "pm",
  887. "discovery",
  888. "workflow"
  889. ],
  890. "strict": false
  891. },
  892. {
  893. "name": "assumption-mapping",
  894. "source": "./skills/assumption-mapping",
  895. "description": "List the assumptions behind an idea and rank them by importance and evidence.",
  896. "category": "discovery",
  897. "tags": [
  898. "pm",
  899. "discovery",
  900. "component"
  901. ],
  902. "strict": false
  903. },
  904. {
  905. "name": "usage-data-investigation",
  906. "source": "./skills/usage-data-investigation",
  907. "description": "Read product usage data honestly: funnel, cohorts, segments, with Fact/Inference/Assumption labels.",
  908. "category": "discovery",
  909. "tags": [
  910. "pm",
  911. "discovery",
  912. "workflow"
  913. ],
  914. "strict": false
  915. },
  916. {
  917. "name": "survey-design-advisor",
  918. "source": "./skills/survey-design-advisor",
  919. "description": "Decide whether a survey is the right tool, then design one that avoids bias.",
  920. "category": "discovery",
  921. "tags": [
  922. "pm",
  923. "discovery",
  924. "interactive"
  925. ],
  926. "strict": false
  927. },
  928. {
  929. "name": "discovery-habits-advisor",
  930. "source": "./skills/discovery-habits-advisor",
  931. "description": "Set up a steady rhythm of customer contact that feeds decisions.",
  932. "category": "discovery",
  933. "tags": [
  934. "pm",
  935. "discovery",
  936. "interactive"
  937. ],
  938. "strict": false
  939. },
  940. {
  941. "name": "pricing-packaging-tracker",
  942. "source": "./skills/pricing-packaging-tracker",
  943. "description": "Track competitor pricing and packaging as a diffable time series: tiers, gates, and what changed.",
  944. "category": "market-intelligence",
  945. "tags": [
  946. "pm",
  947. "market-intelligence",
  948. "pricing",
  949. "monitoring",
  950. "competitive"
  951. ],
  952. "strict": false
  953. },
  954. {
  955. "name": "prioritization-advisor",
  956. "source": "./skills/prioritization-advisor",
  957. "description": "Choose a prioritization framework based on stage, team context, and stakeholder needs.",
  958. "category": "strategy",
  959. "tags": [
  960. "pm",
  961. "prioritization",
  962. "rice",
  963. "scoring"
  964. ],
  965. "strict": false
  966. },
  967. {
  968. "name": "problem-framing-canvas",
  969. "source": "./skills/problem-framing-canvas",
  970. "description": "Guide teams through MITRE's Problem Framing Canvas for clearer problem statements.",
  971. "category": "discovery",
  972. "tags": [
  973. "pm",
  974. "problem-framing",
  975. "mitre",
  976. "workshop"
  977. ],
  978. "strict": false
  979. },
  980. {
  981. "name": "problem-statement",
  982. "source": "./skills/problem-statement",
  983. "description": "Write a user-centered problem statement with who, what, why, and how it feels.",
  984. "category": "discovery",
  985. "tags": [
  986. "pm",
  987. "problem-statement",
  988. "framing",
  989. "empathy"
  990. ],
  991. "strict": false
  992. },
  993. {
  994. "name": "product-lifecycle-plays",
  995. "source": "./skills/product-lifecycle-plays",
  996. "description": "Map lifecycle stage and choose between extension, replacement, and retirement plays.",
  997. "category": "strategy",
  998. "tags": [
  999. "pm",
  1000. "lifecycle",
  1001. "strategy",
  1002. "plc"
  1003. ],
  1004. "strict": false
  1005. },
  1006. {
  1007. "name": "product-sense-interview-answer",
  1008. "source": "./skills/product-sense-interview-answer",
  1009. "description": "Structure a spoken product-sense interview answer with segmentation and MVP tradeoffs.",
  1010. "category": "career",
  1011. "tags": [
  1012. "pm",
  1013. "career",
  1014. "interview",
  1015. "product-sense",
  1016. "product-design"
  1017. ],
  1018. "strict": false
  1019. },
  1020. {
  1021. "name": "product-strategy-session",
  1022. "source": "./skills/product-strategy-session",
  1023. "description": "Run an end-to-end product strategy session across positioning, discovery, and roadmap.",
  1024. "category": "strategy",
  1025. "tags": [
  1026. "pm",
  1027. "strategy",
  1028. "workshop",
  1029. "workflow"
  1030. ],
  1031. "strict": false
  1032. },
  1033. {
  1034. "name": "proto-persona",
  1035. "source": "./skills/proto-persona",
  1036. "description": "Create a proto-persona from current research, market signals, and team knowledge.",
  1037. "category": "discovery",
  1038. "tags": [
  1039. "pm",
  1040. "persona",
  1041. "user-research",
  1042. "assumptions"
  1043. ],
  1044. "strict": false
  1045. },
  1046. {
  1047. "name": "recommendation-canvas",
  1048. "source": "./skills/recommendation-canvas",
  1049. "description": "Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning.",
  1050. "category": "ai",
  1051. "tags": [
  1052. "pm",
  1053. "ai",
  1054. "evaluation",
  1055. "canvas",
  1056. "recommendation"
  1057. ],
  1058. "strict": false
  1059. },
  1060. {
  1061. "name": "roadmap-planning",
  1062. "source": "./skills/roadmap-planning",
  1063. "description": "Plan a strategic roadmap across prioritization, epics, stakeholders, and sequencing.",
  1064. "category": "strategy",
  1065. "tags": [
  1066. "pm",
  1067. "roadmap",
  1068. "planning",
  1069. "workflow"
  1070. ],
  1071. "strict": false
  1072. },
  1073. {
  1074. "name": "saas-economics-efficiency-metrics",
  1075. "source": "./skills/saas-economics-efficiency-metrics",
  1076. "description": "Evaluate SaaS unit economics and capital efficiency for scaling decisions.",
  1077. "category": "finance",
  1078. "tags": [
  1079. "pm",
  1080. "finance",
  1081. "unit-economics",
  1082. "efficiency",
  1083. "saas"
  1084. ],
  1085. "strict": false
  1086. },
  1087. {
  1088. "name": "saas-revenue-growth-metrics",
  1089. "source": "./skills/saas-revenue-growth-metrics",
  1090. "description": "Calculate SaaS revenue, retention, and growth metrics for momentum diagnosis.",
  1091. "category": "finance",
  1092. "tags": [
  1093. "pm",
  1094. "finance",
  1095. "revenue",
  1096. "retention",
  1097. "growth"
  1098. ],
  1099. "strict": false
  1100. },
  1101. {
  1102. "name": "skill-authoring-workflow",
  1103. "source": "./skills/skill-authoring-workflow",
  1104. "description": "Turn raw PM content into a compliant, publish-ready skill.",
  1105. "category": "meta",
  1106. "tags": [
  1107. "pm",
  1108. "skill-authoring",
  1109. "contributor",
  1110. "workflow"
  1111. ],
  1112. "strict": false
  1113. },
  1114. {
  1115. "name": "stakeholder-engagement-advisor",
  1116. "source": "./skills/stakeholder-engagement-advisor",
  1117. "description": "Plan engagement for a specific stakeholder.",
  1118. "category": "strategy",
  1119. "tags": [
  1120. "pm",
  1121. "stakeholders",
  1122. "communication",
  1123. "alignment"
  1124. ],
  1125. "strict": false
  1126. },
  1127. {
  1128. "name": "stakeholder-identification",
  1129. "source": "./skills/stakeholder-identification",
  1130. "description": "Map every stakeholder before engaging anyone.",
  1131. "category": "strategy",
  1132. "tags": [
  1133. "pm",
  1134. "stakeholders",
  1135. "equity",
  1136. "discovery"
  1137. ],
  1138. "strict": false
  1139. },
  1140. {
  1141. "name": "stakeholder-mapping",
  1142. "source": "./skills/stakeholder-mapping",
  1143. "description": "Prioritize stakeholders using two complementary grids.",
  1144. "category": "strategy",
  1145. "tags": [
  1146. "pm",
  1147. "stakeholders",
  1148. "prioritization",
  1149. "alignment"
  1150. ],
  1151. "strict": false
  1152. },
  1153. {
  1154. "name": "storyboard",
  1155. "source": "./skills/storyboard",
  1156. "description": "Create a six-frame storyboard showing a user's journey from problem to solution.",
  1157. "category": "delivery",
  1158. "tags": [
  1159. "pm",
  1160. "storyboard",
  1161. "narrative",
  1162. "ux"
  1163. ],
  1164. "strict": false
  1165. },
  1166. {
  1167. "name": "swot-analysis",
  1168. "source": "./skills/swot-analysis",
  1169. "description": "Evidence-cited SWOT of one company from public sources, ending with the S-O and W-T crossings.",
  1170. "category": "market-intelligence",
  1171. "tags": [
  1172. "pm",
  1173. "market-intelligence",
  1174. "swot",
  1175. "strategy",
  1176. "competitive"
  1177. ],
  1178. "strict": false
  1179. },
  1180. {
  1181. "name": "tam-sam-som-calculator",
  1182. "source": "./skills/tam-sam-som-calculator",
  1183. "description": "Calculate TAM, SAM, and SOM with explicit assumptions, methods, and caveats.",
  1184. "category": "strategy",
  1185. "tags": [
  1186. "pm",
  1187. "market-sizing",
  1188. "tam",
  1189. "business-case"
  1190. ],
  1191. "strict": false
  1192. },
  1193. {
  1194. "name": "user-story",
  1195. "source": "./skills/user-story",
  1196. "description": "Create user stories with Mike Cohn format and Gherkin acceptance criteria.",
  1197. "category": "delivery",
  1198. "tags": [
  1199. "pm",
  1200. "user-stories",
  1201. "acceptance-criteria",
  1202. "gherkin"
  1203. ],
  1204. "strict": false
  1205. },
  1206. {
  1207. "name": "user-story-mapping",
  1208. "source": "./skills/user-story-mapping",
  1209. "description": "Create a user story map with activities, steps, tasks, and release slices.",
  1210. "category": "delivery",
  1211. "tags": [
  1212. "pm",
  1213. "story-mapping",
  1214. "backlog",
  1215. "mvp"
  1216. ],
  1217. "strict": false
  1218. },
  1219. {
  1220. "name": "user-story-mapping-workshop",
  1221. "source": "./skills/user-story-mapping-workshop",
  1222. "description": "Run a user story mapping workshop with adaptive questions and structured output.",
  1223. "category": "delivery",
  1224. "tags": [
  1225. "pm",
  1226. "story-mapping",
  1227. "workshop",
  1228. "facilitation"
  1229. ],
  1230. "strict": false
  1231. },
  1232. {
  1233. "name": "user-story-splitting",
  1234. "source": "./skills/user-story-splitting",
  1235. "description": "Break a large story into smaller deliverable stories using proven split patterns.",
  1236. "category": "delivery",
  1237. "tags": [
  1238. "pm",
  1239. "splitting",
  1240. "user-stories",
  1241. "backlog"
  1242. ],
  1243. "strict": false
  1244. },
  1245. {
  1246. "name": "voice-of-customer-miner",
  1247. "source": "./skills/voice-of-customer-miner",
  1248. "description": "Mine public reviews, app stores, and forums for unmet needs and competitor weaknesses, with quoted evidence.",
  1249. "category": "market-intelligence",
  1250. "tags": [
  1251. "pm",
  1252. "market-intelligence",
  1253. "voc",
  1254. "discovery",
  1255. "reviews"
  1256. ],
  1257. "strict": false
  1258. },
  1259. {
  1260. "name": "vp-cpo-readiness-advisor",
  1261. "source": "./skills/vp-cpo-readiness-advisor",
  1262. "description": "Guide the transition to VP or CPO across preparing, interviewing, and recalibrating.",
  1263. "category": "career",
  1264. "tags": [
  1265. "pm",
  1266. "career",
  1267. "vp",
  1268. "cpo",
  1269. "executive",
  1270. "coaching"
  1271. ],
  1272. "strict": false
  1273. },
  1274. {
  1275. "name": "workshop-facilitation",
  1276. "source": "./skills/workshop-facilitation",
  1277. "description": "Facilitate workshop sessions with consistent pacing, options, and progress tracking.",
  1278. "category": "meta",
  1279. "tags": [
  1280. "pm",
  1281. "facilitation",
  1282. "workshop",
  1283. "interactive"
  1284. ],
  1285. "strict": false
  1286. },
  1287. {
  1288. "name": "sprint-planning",
  1289. "source": "./skills/sprint-planning",
  1290. "description": "Plan a sprint around a goal, real capacity, and named risks.",
  1291. "category": "delivery",
  1292. "tags": [
  1293. "pm",
  1294. "sprint",
  1295. "workflow"
  1296. ],
  1297. "strict": false
  1298. },
  1299. {
  1300. "name": "backlog-refinement-advisor",
  1301. "source": "./skills/backlog-refinement-advisor",
  1302. "description": "Get backlog items ready for planning",
  1303. "category": " understood, small, testable.",
  1304. "tags": [
  1305. "pm",
  1306. "delivery:backlog",
  1307. "interactive"
  1308. ],
  1309. "strict": false
  1310. },
  1311. {
  1312. "name": "release-readiness",
  1313. "source": "./skills/release-readiness",
  1314. "description": "Check a release is safe to ship",
  1315. "category": " tests, rollout, monitoring, rollback, support.",
  1316. "tags": [
  1317. "pm",
  1318. "delivery:release",
  1319. "component"
  1320. ],
  1321. "strict": false
  1322. },
  1323. {
  1324. "name": "decision-rights-matrix",
  1325. "source": "./skills/decision-rights-matrix",
  1326. "description": "Define who decides what for key product decisions, with one accountable person each.",
  1327. "category": "stakeholder",
  1328. "tags": [
  1329. "pm",
  1330. "decisions",
  1331. "raci",
  1332. "component"
  1333. ],
  1334. "strict": false
  1335. },
  1336. {
  1337. "name": "pm-role-charter",
  1338. "source": "./skills/pm-role-charter",
  1339. "description": "Write a one-page charter for a PM role",
  1340. "category": " outcome, decisions, interfaces, measures.",
  1341. "tags": [
  1342. "pm",
  1343. "stakeholder:role",
  1344. "charter",
  1345. "component"
  1346. ],
  1347. "strict": false
  1348. },
  1349. {
  1350. "name": "activation-design",
  1351. "source": "./skills/activation-design",
  1352. "description": "Define the first-real-value moment and design the shortest path to it.",
  1353. "category": "delivery",
  1354. "tags": [
  1355. "pm",
  1356. "activation",
  1357. "onboarding",
  1358. "component"
  1359. ],
  1360. "strict": false
  1361. },
  1362. {
  1363. "name": "retention-diagnostic-advisor",
  1364. "source": "./skills/retention-diagnostic-advisor",
  1365. "description": "Find why customers leave or go quiet, then pick the fix that fits the cause.",
  1366. "category": "delivery",
  1367. "tags": [
  1368. "pm",
  1369. "retention",
  1370. "churn",
  1371. "interactive"
  1372. ],
  1373. "strict": false
  1374. }
  1375. ]
  1376. }
README.md · README · 402 lines
  1. <a id="pmskills"></a>
  2. # Product Manager Skills
  3. **Ready-made PM skills for your AI assistant.** A *skill* is a short instruction file that teaches an AI how to do one PM job the way a pro would, such as writing a PRD or mapping stakeholders, so you stop re-explaining your process every time.
  4. ## Try it in five minutes
  5. 1. Download the [starter pack](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-skills-starter-pack.zip) and unzip it.
  6. 2. In Claude, open **Settings → Capabilities → Skills** and upload one skill ZIP from inside the folder. Using Claude Code, Codex or something else? Jump to [Get Started](#get-started).
  7. 3. Start a chat and paste this, swapping in your own details:
  8. ```text
  9. Which of these skills fits what's on my desk this week? Here's the situation: [one or two sentences].
  10. ```
  11. You should see Claude name the skill it is using and start asking you questions. Arriving empty-handed is fine: the skills ask for what they need.
  12. ---
  13. [![GitHub stars](https://img.shields.io/github/stars/deanpeters/Product-Manager-Skills?style=flat-square)](https://github.com/deanpeters/Product-Manager-Skills/stargazers) [![GitHub forks](https://img.shields.io/github/forks/deanpeters/Product-Manager-Skills?style=flat-square)](https://github.com/deanpeters/Product-Manager-Skills/forks) [![GitHub watchers](https://img.shields.io/github/watchers/deanpeters/Product-Manager-Skills?style=flat-square)](https://github.com/deanpeters/Product-Manager-Skills/watchers) [![Contributors](https://img.shields.io/github/contributors/deanpeters/Product-Manager-Skills?style=flat-square)](https://github.com/deanpeters/Product-Manager-Skills/graphs/contributors) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen?style=flat-square)](CONTRIBUTING.md)
  14. [![Version](https://img.shields.io/badge/version-v0.86-blue?style=flat-square)](https://github.com/deanpeters/Product-Manager-Skills/releases/latest) ![Skills](https://img.shields.io/badge/skills-95-informational?style=flat-square) [![Last commit](https://img.shields.io/github/last-commit/deanpeters/Product-Manager-Skills?style=flat-square)](https://github.com/deanpeters/Product-Manager-Skills/commits/main) [![Claude Code Plugin](https://img.shields.io/badge/Claude%20Code-Plugin%20Marketplace-5C4EE5?style=flat-square)](https://code.claude.com/docs/en/plugin-marketplaces)
  15. ```text
  16. ╔════════════════════════════════════════════════════════════════════╗
  17. ║ ║
  18. ║ ██████╗ ███╗ ███╗ ███████╗██╗ ██╗██╗██╗ ██╗ ███████╗
  19. ║ ██╔══██╗████╗ ████║ ██╔════╝██║ ██╔╝██║██║ ██║ ██╔════╝
  20. ║ ██████╔╝██╔████╔██║ ███████╗█████╔╝ ██║██║ ██║ ███████╗
  21. ║ ██╔═══╝ ██║╚██╔╝██║ ╚════██║██╔═██╗ ██║██║ ██║ ╚════██║
  22. ║ ██║ ██║ ╚═╝ ██║ ███████║██║ ██╗██║███████╗███████╗███████║
  23. ║ ╚═╝ ╚═╝ ╚═╝ ╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝╚══════╝
  24. ║ ║
  25. ║ 95 battle-tested skills + 6 command workflows ║
  26. ║ Claude Code • Cursor • Codex • n8n • OpenClaw • and more ... ║
  27. ║ ║
  28. ║ v0.86 • November 13, 2026 • CC BY-NC-SA 4.0 ║
  29. ╚════════════════════════════════════════════════════════════════════╝
  30. ```
  31. **95 battle-tested PM frameworks, ready for Claude, Codex, ChatGPT, and any agent that can read structured knowledge.**
  32. ---
  33. ## Why This Exists
  34. Generic AI output is a PM's worst enemy. When you tell your agent "write a PRD" without shared context, you get a generic document that no stakeholder trusts and no engineer can act on.
  35. This library gives both you and your AI agent the same professional foundation: the *why* behind each framework, the failure modes to avoid, and the judgment to apply them correctly. You stop repeating yourself. Your agent stops guessing. The work gets better.
  36. **The goal is dual — functional and pedagogic in equal measure.** Skills equip agents to do PM work at a professional level, and they teach the human PM the reasoning behind each framework — so you can explain it, adapt it, and pass it on. Neither is a byproduct of the other.
  37. ---
  38. ## Get Started
  39. Choose your setup:
  40. | I use... | Get this | Notes |
  41. |---|---|---|
  42. | Claude Desktop or Claude Web | [`pm-skills-starter-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-skills-starter-pack.zip) | Unzip, then upload the individual skill ZIPs to Claude Skills |
  43. | Claude Code | Plugin marketplace | `/plugin marketplace add deanpeters/Product-Manager-Skills`, then `/plugin install product-manager-skills@pm-skills` for everything, or one lifecycle bundle at a time (see [Browse by lifecycle](#browse-by-lifecycle)) |
  44. | Codex | [`pm-skills-codex.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-skills-codex.zip) | Installs `.agents/skills` and `AGENTS.md` |
  45. | OpenCode | Copy `skills/*` to `~/.config/opencode/skills/` (or reuse the Codex ZIP) | OpenCode reads our `SKILL.md` format as-is. See the [install guide](docs/INSTALL-OPENCODE.md) |
  46. | Not sure | [`pm-skills-starter-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-skills-starter-pack.zip) | Start here |
  47. **All downloads:** [GitHub Releases](https://github.com/deanpeters/Product-Manager-Skills/releases/latest)
  48. ### Start here by situation
  49. Don't know where to begin? Find the line that sounds like your week. Each route is **a suggested order, not a pipeline** — every skill runs on its own, so skip ahead, reorder, or stop after one. The first prompt is real: paste it, swap in your details, and go.
  50. | If this is you... | Try, in this order | Time | Paste this first |
  51. |---|---|---|---|
  52. | **"I have an idea and I don't know if it's real."** | [problem-framing-canvas](skills/problem-framing-canvas/SKILL.md) → [discovery-interview-prep](skills/discovery-interview-prep/SKILL.md) → [pol-probe-advisor](skills/pol-probe-advisor/SKILL.md) | ~1–1.5 hr | `Frame this problem: field sales reps 'don't use the CRM' and leadership wants gamification.` |
  53. | **"A request or mandate just landed on my desk."** | [incoming-request-advisor](skills/incoming-request-advisor/SKILL.md) → [stakeholder-mapping](skills/stakeholder-mapping/SKILL.md) → [prioritization-advisor](skills/prioritization-advisor/SKILL.md) | ~1 hr | `My VP DM'd me: "Any chance the dashboard redesign lands next sprint? Board's asking." Analyze this before I reply.` |
  54. | **"I need to understand the market, fast."** | [market-landscape-scan](skills/market-landscape-scan/SKILL.md) → [competitive-research-snapshot](skills/competitive-research-snapshot/SKILL.md) → [swot-analysis](skills/swot-analysis/SKILL.md) | ~1–2 hr | `Run a market landscape scan on [your market], and tell me the decision it should support.` |
  55. | **"We keep getting compared and losing."** | [positioning-workshop](skills/positioning-workshop/SKILL.md) → [roadmap-planning](skills/roadmap-planning/SKILL.md) *(going bigger: [product-strategy-session](skills/product-strategy-session/SKILL.md), a 2–4 week workflow)* | ~2–3 hr | `Run a positioning workshop for our API monitoring tool — we keep getting compared to Datadog and losing.` |
  56. | **"Time to write it down."** | [prd-development](skills/prd-development/SKILL.md) → [epic-breakdown-advisor](skills/epic-breakdown-advisor/SKILL.md) → [user-story](skills/user-story/SKILL.md) | ~1.5–3 hr | `Build a PRD for self-serve workspace provisioning — here are my discovery notes and the OKR it ladders to.` |
  57. | **"Our product is getting old."** | [lifecycle-play-advisor](skills/lifecycle-play-advisor/SKILL.md) → [eol-readiness-advisor](skills/eol-readiness-advisor/SKILL.md) → [eol-process](skills/eol-process/SKILL.md) | ~30–50 min to a decision | `Help me decide what to do with [product]. Here's what makes me think it's fading: [signals].` |
  58. | **"I'm stepping up a level."** | [director-readiness-advisor](skills/director-readiness-advisor/SKILL.md) *or* [vp-cpo-readiness-advisor](skills/vp-cpo-readiness-advisor/SKILL.md) — pick by where you're headed | ~10–20 min | `I'm 60 days into a Director role and my old peers now report to me — it's awkward and I'm still doing PM work. Coach me.` |
  59. | **"I'm new here, or not sure."** | The [Starter pack](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-skills-starter-pack.zip) — six skills across the craft | — | Install it, then ask: `Which of these skills fits what's on my desk this week?` |
  60. **Why these orders (so you can break them on purpose):**
  61. - **Idea → problem → people → probe.** Name the problem before you ask anyone about it, and ask people before you build anything. The probe comes last because it's the most expensive of the three.
  62. - **Request → decode → map → decide.** Understand what's really being asked before replying, know who else is in the room, *then* ask where it fits. Prioritizing first is how a loud VP becomes your roadmap.
  63. - **Market → competitors → SWOT.** Evidence first, framework last. SWOT on top of no research is opinion with a 2×2 around it.
  64. - **Positioning → roadmap.** Decide who you're for and why you win before choosing what to build. The strategy session is the full-length version when the question is bigger than a quarter.
  65. - **PRD → epics → stories.** The *why* first, then slices, then the smallest writeable pieces. Writing stories first is how a backlog loses its reason.
  66. - **Aging → play → readiness → process.** The first skill may say **"nothing yet"** — extending or harvesting is a legitimate answer, and starting here does not commit you to a sunset.
  67. ### Browse by lifecycle
  68. Product work unfolds in an order: set the outcome before you investigate, investigate before you define, define before you build. The library follows that arc in five bundles, with a sixth that runs underneath all of them. It's a cycle, not a pipeline, so you will loop back, and every skill still runs on its own.
  69. | Bundle | The question it answers | Start with | Claude Code install |
  70. |---|---|---|---|
  71. | **Determine** | What are we trying to achieve, and what is the market doing? | [product-strategy-session](skills/product-strategy-session/SKILL.md), [market-landscape-scan](skills/market-landscape-scan/SKILL.md), [business-health-diagnostic](skills/business-health-diagnostic/SKILL.md) | `/plugin install pm-determine@pm-skills` |
  72. | **Discover** | What is the real problem? | [problem-framing-canvas](skills/problem-framing-canvas/SKILL.md), [discovery-interview-prep](skills/discovery-interview-prep/SKILL.md) | `/plugin install pm-discover@pm-skills` |
  73. | **Define** | Is this solution worth building, and how do we position it? | [pol-probe-advisor](skills/pol-probe-advisor/SKILL.md), [positioning-statement](skills/positioning-statement/SKILL.md) | `/plugin install pm-define@pm-skills` |
  74. | **Develop** | How do we turn the chosen solution into buildable work? | [prd-development](skills/prd-development/SKILL.md), [user-story](skills/user-story/SKILL.md), [prioritization-advisor](skills/prioritization-advisor/SKILL.md) | `/plugin install pm-develop@pm-skills` |
  75. | **Deliver** | How do we price it, take it to market, and retire it well? | [finance-based-pricing-advisor](skills/finance-based-pricing-advisor/SKILL.md), [lifecycle-play-advisor](skills/lifecycle-play-advisor/SKILL.md) | `/plugin install pm-deliver@pm-skills` |
  76. | **Drive** | How do I work with stakeholders and grow my career? | [stakeholder-mapping](skills/stakeholder-mapping/SKILL.md), [director-readiness-advisor](skills/director-readiness-advisor/SKILL.md) | `/plugin install pm-drive@pm-skills` |
  77. **Not sure which bundle?** Ask the [pm-skills-navigator](skills/pm-skills-navigator/SKILL.md): describe what's on your desk, and in about five minutes it tells you where the work really is and which skill to open first.
  78. Every bundle includes a few shared helper skills (the facilitation rulebook and the navigator among them), so each works installed alone. The full list, grouped by bundle and by the smaller "motions" inside each, is in [catalog/skills-by-bundle.md](catalog/skills-by-bundle.md).
  79. *Why this order?* Skipping ahead is how teams build the right thing for the wrong problem. Naming the outcome first gives discovery a target, and discovery gives definition something real to test.
  80. **On Claude Desktop or Web?** Download the bundle pack that matches your phase, or grab single skills from the [download shelf](dist/).
  81. ### Lifecycle bundle packs for Claude Desktop / Web
  82. Each pack is a ZIP of upload-ready skill ZIPs. Unzip it, then upload the skills to Claude Skills:
  83. | Pack | Download | What's inside |
  84. |---|---|---|
  85. | Starter | [`pm-skills-starter-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-skills-starter-pack.zip) | Six core skills across the craft. The best first download |
  86. | Determine | [`pm-determine-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-determine-pack.zip) | Strategy, finance, market intelligence, customer context (24 skills) |
  87. | Discover | [`pm-discover-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-discover-pack.zip) | Interviews, surveys, usage data, synthesis, assumptions, problem framing, opportunity trees, journey maps (12 skills) |
  88. | Define | [`pm-define-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-define-pack.zip) | Hypotheses, probes, experiments, positioning (9 skills) |
  89. | Develop | [`pm-develop-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-develop-pack.zip) | PRDs, stories, prioritization, roadmaps, sprint and release rituals, AI agents (16 skills) |
  90. | Deliver | [`pm-deliver-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-deliver-pack.zip) | Launch plans, messaging, sales enablement, pricing, channels, post-launch metrics, activation and retention, and the end-of-life suite (18 skills) |
  91. | Drive | [`pm-drive-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/pm-drive-pack.zip) | Stakeholders, decision rights, influence, and career transitions (11 skills) |
  92. | All skills | [`99-all-skills-pack.zip`](https://github.com/deanpeters/Product-Manager-Skills/releases/latest/download/99-all-skills-pack.zip) | All 95 skills |
  93. The older themed packs (`02-discovery` through `07-lifecycle-eol`) were retired in v0.86. Every skill in them lives in a lifecycle pack above.
  94. ### Install guides
  95. - [Claude Desktop / Web](docs/INSTALL-CLAUDE-DESKTOP.md)
  96. - [Claude Code](docs/INSTALL-CLAUDE-CODE.md)
  97. - [Codex](docs/INSTALL-CODEX.md)
  98. - [OpenCode](docs/INSTALL-OPENCODE.md)
  99. - [Platform chooser for non-technical PMs](docs/PM%20Skills%20Rule-of-Thumb%20Guide.md)
  100. ---
  101. ## Try It First — Streamlit (beta)
  102. Not ready to wire skills into your agent setup? Run the local playground first and kick the tires in your browser.
  103. ```bash
  104. pip install -r app/requirements.txt
  105. streamlit run app/main.py
  106. ```
  107. What you can do:
  108. - **Learn** — browse setup and integration paths without leaving the app
  109. - **Find My Skill** — describe your situation in plain English and get recommended skills
  110. - **Run Skills** — run a skill with your own scenario once you know what you want
  111. Multi-provider support: Anthropic, OpenAI, Ollama. API keys via environment variables only (no in-app key entry).
  112. Docs: [`app/STREAMLIT_INTERFACE.md`](app/STREAMLIT_INTERFACE.md) · [`app/.env.example`](app/.env.example)
  113. Feedback welcome via [GitHub Issues](https://github.com/deanpeters/Product-Manager-Skills/issues) or [LinkedIn](https://linkedin.com/in/deanpeters).
  114. ---
  115. ## What You Can Get Done
  116. Navigate by what you're actually trying to accomplish:
  117. **Framing and strategy**
  118. - [problem-framing-canvas](skills/problem-framing-canvas/SKILL.md) — MITRE's Look Inward / Look Outward / Reframe sequence; stops teams from solving the wrong problem
  119. - [positioning-statement](skills/positioning-statement/SKILL.md) — Geoffrey Moore's template for defining who you serve, what you solve, and how you're different
  120. - [product-strategy-session](skills/product-strategy-session/SKILL.md) — full strategy arc: positioning → problem framing → solution exploration → roadmap (2-4 weeks)
  121. **Stakeholder alignment**
  122. - [stakeholder-identification](skills/stakeholder-identification/SKILL.md) — map every stakeholder before engaging anyone: broad brainstorm → allies/audiences/influencers → R/P/D marking → equity lens → narrow to priority targets
  123. - [stakeholder-mapping](skills/stakeholder-mapping/SKILL.md) — run two complementary grids (Power × Interest for engagement strategy; Impact × Power for whose voice to elevate) and compare to find the gaps
  124. - [stakeholder-engagement-advisor](skills/stakeholder-engagement-advisor/SKILL.md) — per-stakeholder engagement planning: diagnoses their profile and context, then delivers tailored message framing, medium, cadence, and a named next action
  125. **Customer discovery and research**
  126. - [discovery-interview-prep](skills/discovery-interview-prep/SKILL.md) — plans Mom Test-style interviews based on your research goals
  127. - [opportunity-solution-tree](skills/opportunity-solution-tree/SKILL.md) — generates opportunities and solutions, then recommends the best proof-of-concept to test first
  128. - [discovery-process](skills/discovery-process/SKILL.md) — complete discovery cycle: frame → research → synthesize → validate (3-4 weeks)
  129. **Prioritization and roadmapping**
  130. - [prioritization-advisor](skills/prioritization-advisor/SKILL.md) — asks 3-5 questions about your context, then recommends RICE, ICE, Kano, or the right alternative
  131. - [epic-breakdown-advisor](skills/epic-breakdown-advisor/SKILL.md) — splits large epics using Richard Lawrence's 9 patterns
  132. - [roadmap-planning](skills/roadmap-planning/SKILL.md) — gather inputs → define epics → prioritize → sequence → communicate (1-2 weeks)
  133. **Writing PM deliverables**
  134. - [user-story](skills/user-story/SKILL.md) — Mike Cohn format + Gherkin acceptance criteria, with anti-patterns
  135. - [prd-development](skills/prd-development/SKILL.md) — structured PRD: problem → personas → solution → metrics → stories (2-4 days)
  136. - [press-release](skills/press-release/SKILL.md) — Amazon Working Backwards: clarify product vision before writing a line of spec
  137. **Validation and experimentation**
  138. - [pol-probe-advisor](skills/pol-probe-advisor/SKILL.md) — recommends which prototype type to run based on your hypothesis and risk level
  139. - [pol-probe](skills/pol-probe/SKILL.md) — template for documenting lightweight validation experiments before building
  140. **Finance and growth**
  141. - [business-health-diagnostic](skills/business-health-diagnostic/SKILL.md) — diagnoses SaaS health across growth, retention, efficiency, and capital using your real metrics
  142. - [organic-growth-advisor](skills/organic-growth-advisor/SKILL.md) — McKinsey Growth Pyramid triage: diagnoses whether your constraint is in new segments, geographies, channels, or products
  143. - [feature-investment-advisor](skills/feature-investment-advisor/SKILL.md) — build / don't build recommendation using revenue impact, cost, ROI, and strategic value
  144. **Market and competitive intelligence**
  145. - [intel-discipline-advisor](skills/intel-discipline-advisor/SKILL.md) — start here: triages the question on your desk into the right intelligence disciplines, cadence, and executing skill
  146. - [competitive-analysis-process](skills/competitive-analysis-process/SKILL.md) — the six-step umbrella: landscape → product comparison → customer needs → business baseline → positioning → strategic direction
  147. - The investigation chain: [market-landscape-scan](skills/market-landscape-scan/SKILL.md) → [competitive-research-snapshot](skills/competitive-research-snapshot/SKILL.md) → [competitive-intel-watch](skills/competitive-intel-watch/SKILL.md) → [battle-card-builder](skills/battle-card-builder/SKILL.md) — each consumes the prior's schema, so research becomes a cadence instead of a one-off deck
  148. - [tam-sam-som-calculator](skills/tam-sam-som-calculator/SKILL.md) — market sizing three ways: your own numbers, guided interview, or autonomous bottom-up research a skeptical CFO can attack one assumption at a time
  149. **Aging products: extend, replace, or retire**
  150. - [lifecycle-play-advisor](skills/lifecycle-play-advisor/SKILL.md) — start here when a product stops growing: seven transition questions establish the stage, then it picks the play — extend, replace, or retire — and tells you when the honest answer is "nothing yet"
  151. - [product-lifecycle-plays](skills/product-lifecycle-plays/SKILL.md) — the framework behind that call: the PLC strategy grid, the seven replacement hazards, and a risk register whose last column asks *what is Plan B?*
  152. - [eol-process](skills/eol-process/SKILL.md) — the whole sunset in six phases, decide → align → plan → prepare → announce → close, including the post-EOL review everyone skips
  153. - The EOL chain: [eol-readiness-advisor](skills/eol-readiness-advisor/SKILL.md) → [eol-stakeholder-sequence](skills/eol-stakeholder-sequence/SKILL.md) → [eol-checklist](skills/eol-checklist/SKILL.md) → [eol-internal-enablement](skills/eol-internal-enablement/SKILL.md) → [eol-message](skills/eol-message/SKILL.md) — every one runs standalone, sized Light/Standard/Heavy by you
  154. **Career and leadership transitions**
  155. - [director-readiness-advisor](skills/director-readiness-advisor/SKILL.md) — coaches PMs through the PM→Director shift across four situations: preparing, interviewing, newly landed, recalibrating
  156. - [vp-cpo-readiness-advisor](skills/vp-cpo-readiness-advisor/SKILL.md) — coaches Directors through VP/CPO transition, including a CEO interview framework for evaluating roles before you accept
  157. - [executive-onboarding-playbook](skills/executive-onboarding-playbook/SKILL.md) — 30-60-90 day diagnostic playbook for VP/CPO transitions
  158. **AI product work**
  159. - [ai-shaped-readiness-advisor](skills/ai-shaped-readiness-advisor/SKILL.md) — assesses whether you're automating tasks (AI-first) or redesigning how you work (AI-shaped), then tells you which competency to build first
  160. - [context-engineering-advisor](skills/context-engineering-advisor/SKILL.md) — diagnoses context stuffing vs. context engineering and guides memory architecture for AI-powered products
  161. - [agent-orchestration-advisor](skills/agent-orchestration-advisor/SKILL.md) — guides multi-agent workflow design across four dimensions
  162. ---
  163. ## 95 Skills, 3 Types
  164. Skills are organized in three tiers that build on each other:
  165. ```
  166. ┌────────────────────────────────────────────────────────┐
  167. │ WORKFLOW SKILLS (25) │
  168. │ Complete end-to-end PM processes (days to weeks) │
  169. │ Example: run a full discovery cycle or write a PRD │
  170. └────────────────────────────────────────────────────────┘
  171. ↓ orchestrates
  172. ┌────────────────────────────────────────────────────────┐
  173. │ INTERACTIVE SKILLS (34) │
  174. │ Guided discovery — 3-5 questions, then recommendations│
  175. │ Example: "Which prioritization framework fits here?" │
  176. └────────────────────────────────────────────────────────┘
  177. ↓ uses
  178. ┌────────────────────────────────────────────────────────┐
  179. │ COMPONENT SKILLS (36) │
  180. │ Templates for specific PM deliverables (30-90 min) │
  181. │ Example: write a user story with acceptance criteria │
  182. └────────────────────────────────────────────────────────┘
  183. ```
  184. **Interactive skills use an Adaptive Decision Ladder.** Instead of dumping a framework at you, an interactive skill asks 3-5 targeted questions about your specific context, then offers numbered recommendations — each with a clear "use this when" rationale. You pick a path. The skill executes it and explains the *why* as it goes. If you want to just learn the framework without doing the work, you can ask that too — the skill coaches you either way. This is ABC — Always Be Coaching — in practice.
  185. **Full catalog:** [by type](catalog/skills-by-type.md) or [by lifecycle bundle](catalog/skills-by-bundle.md), all 95 skills with descriptions, or browse `skills/` directly.
  186. ---
  187. ## How a Skill File Works
  188. Every `SKILL.md` follows the same structure:
  189. | Section | What it contains |
  190. |---|---|
  191. | **Frontmatter** | `name`, `description`, `type`, `intent`, `best_for`, `scenarios` |
  192. | **Purpose** | What this skill does and when to reach for it |
  193. | **Input** | What you *can* bring (with example invocations) — inline input is used, not re-asked, and arriving empty-handed is fine: the skill walks you through it |
  194. | **Key Concepts** | Frameworks, definitions, anti-patterns — with vocabulary explained |
  195. | **Application** | Step-by-step instructions an agent (or human) can follow |
  196. | **Examples** | Real-world cases showing both good and bad versions |
  197. | **Common Pitfalls** | Named failure modes with consequences and corrections |
  198. | **References** | Related skills and external frameworks |
  199. The `best_for` frontmatter field lists 3-5 specific scenarios where the skill is most useful — helpful for quickly scanning whether a skill fits your situation.
  200. **Why no `$ARGUMENTS` templating?** Other skill libraries use Claude Code's `$ARGUMENTS` substitution for input. We deliberately don't: it only expands in Claude Code (it renders as literal syntax in Claude Desktop/Web, Codex, and the Streamlit playground), and it teaches the human reader nothing. Instead, every skill has a plain-language `## Input` section that works on every runtime — and makes clear you can show up with full context, partial context, or nothing at all and be guided through the rest. Full rationale in [CONTRIBUTING.md](CONTRIBUTING.md).
  201. **Guided Context Capture.** Every interactive skill gathers context the same way. You can go one question at a time, paste what you know, or say "best guess." A pasted dump gets read back to you as Known / Assumed / Missing / Conflicting before any question is asked. You get a recap before anything is generated. Decisions come as a ranked ladder (Recommended first, real alternatives with tradeoffs), and you make the call. The skill never re-asks what you already said or passes a guess off as a fact. Guided is the default opening; change it library-wide or per skill in [`pm-skills.config.yaml`](pm-skills.config.yaml). How it works and why: [docs/guided-context-capture.md](docs/guided-context-capture.md).
  202. ---
  203. ## Works With
  204. Claude Code · Claude Desktop · Claude Web · OpenAI Codex · ChatGPT · Cursor · Windsurf · n8n · LangFlow · CrewAI · Gemini · OpenCode · any agent that reads structured markdown
  205. See [docs/Platform Guides for PMs.md](docs/Platform%20Guides%20for%20PMs.md) for platform-specific setup.
  206. ---
  207. ## Docs
  208. | Document | Purpose |
  209. |---|---|
  210. | [Using PM Skills 101](docs/Using%20PM%20Skills%20101.md) | Beginner-friendly orientation — setup without technical overload |
  211. | [Platform Guides for PMs](docs/Platform%20Guides%20for%20PMs.md) | Tool-by-tool setup chooser for every supported platform |
  212. | [Using PM Skills with Claude](docs/Using%20PM%20Skills%20with%20Claude.md) | Claude Code + GitHub ZIP upload for Claude Desktop/Web |
  213. | [Using PM Skills with Codex](docs/Using%20PM%20Skills%20with%20Codex.md) | Local workspace + GitHub-connected Codex on ChatGPT |
  214. | [Using PM Skills with ChatGPT](docs/Using%20PM%20Skills%20with%20ChatGPT.md) | GitHub app, Custom GPT Knowledge, and Project-based usage |
  215. | [Using PM Skills with Slash Commands 101](docs/Using%20PM%20Skills%20with%20Slash%20Commands%20101.md) | Turn skills into reusable slash commands like `/pm-story` |
  216. | [Add-a-Skill Utility Guide](docs/Add-a-Skill%20Utility%20Guide.md) | End-to-end guide for generating and validating new skills |
  217. | [Market Intelligence Suite Summary](docs/Market%20Intelligence%20Suite%20Summary.md) | The 14-skill competitive/market research suite: disciplines, chain, and which skill to run when |
  218. | [Lifecycle & EOL Suite Summary](docs/Lifecycle%20and%20EOL%20Suite%20Summary.md) | The 8-skill lifecycle/sunset suite: the three plays, the EOL chain, and right-sizing |
  219. | [Building PM Skills](docs/Building%20PM%20Skills.md) | How raw PM content gets distilled into agent-ready skills |
  220. | [START_HERE.md](START_HERE.md) | 60-second onboarding for local repo users |
  221. ---
  222. ## What's New
  223. **v0.86 — November 13, 2026 · The Everyday Work of Product, Now on the Map**
  224. - **12 new skills fill the map:** Discover gains *Dig* ([`survey-design-advisor`](skills/survey-design-advisor/SKILL.md), [`usage-data-investigation`](skills/usage-data-investigation/SKILL.md), [`discovery-habits-advisor`](skills/discovery-habits-advisor/SKILL.md)) and *Decode* ([`research-synthesis`](skills/research-synthesis/SKILL.md), [`assumption-mapping`](skills/assumption-mapping/SKILL.md)); Develop gains *Drumbeat* ([`backlog-refinement-advisor`](skills/backlog-refinement-advisor/SKILL.md), [`sprint-planning`](skills/sprint-planning/SKILL.md), [`release-readiness`](skills/release-readiness/SKILL.md)); Drive gains *Delineate* ([`decision-rights-matrix`](skills/decision-rights-matrix/SKILL.md), [`pm-role-charter`](skills/pm-role-charter/SKILL.md)); Deliver gains *Deepen* ([`activation-design`](skills/activation-design/SKILL.md), [`retention-diagnostic-advisor`](skills/retention-diagnostic-advisor/SKILL.md))
  225. - **Pick your slice, not all 95:** agents are converging on installable plugins and bundles, so the lifecycle bundles let you install what matches your work
  226. - **Easier to start:** a five-minute path on the README's first screen, a layered `START_HERE.md`, a clearer Desktop install, and a docs style guard
  227. - **Older packs `02`-`07` retired;** every skill in them lives in a lifecycle bundle
  228. - Library at **95 skills** · full story in the [release note](docs/announcements/2026-11-13-v0-86-the-everyday-work-of-product.md)
  229. **v0.85 — November 13, 2026 · Lifecycle Bundles, a Navigator, and the Go-to-Market Gap Filled**
  230. - **Six installable lifecycle bundles** that follow the product arc: Determine, Discover, Define, Develop, Deliver, plus Drive (stakeholders and career) underneath. Install one with `/plugin install pm-define@pm-skills`, or download its pack for Claude Desktop. Every skill still runs on its own
  231. - **[`pm-skills-navigator`](skills/pm-skills-navigator/SKILL.md):** describe what's on your desk and get routed to the right phase and skill
  232. - **Go-to-market, filled:** [`launch-plan`](skills/launch-plan/SKILL.md), [`launch-metrics`](skills/launch-metrics/SKILL.md), [`message-house`](skills/message-house/SKILL.md), [`sales-value-narrative`](skills/sales-value-narrative/SKILL.md), [`buying-journey-enablement`](skills/buying-journey-enablement/SKILL.md)
  233. - Also: [`LICENSING.md`](LICENSING.md), an [OpenCode install guide](docs/INSTALL-OPENCODE.md), and drift guards for prose counts
  234. - Library now at **83 skills** · full story in the [release note](docs/announcements/2026-11-13-v0-85-lifecycle-bundles.md)
  235. **v0.84 — August 10, 2026 · The Lifecycle & End-of-Life Suite**
  236. - **7 new skills + 1 upgrade** for the part of product management nobody trains you on: what to do with a product that has stopped growing, and how to retire one without losing the customer
  237. - Start upstream of the kill decision. [`lifecycle-play-advisor`](skills/lifecycle-play-advisor/SKILL.md) and [`product-lifecycle-plays`](skills/product-lifecycle-plays/SKILL.md) diagnose where a product actually sits using seven transition questions, then pick between the three plays — **extend, replace, or retire**. Includes the seven replacement hazards and a risk register whose contingency column asks the question everyone skips: *what is Plan B?*
  238. - The EOL chain: [`eol-readiness-advisor`](skills/eol-readiness-advisor/SKILL.md) (go/no-go, and it will tell you to hold) → [`eol-stakeholder-sequence`](skills/eol-stakeholder-sequence/SKILL.md) (Legal before Finance before Sales — get the order wrong and you find the landmines after the announcement) → [`eol-checklist`](skills/eol-checklist/SKILL.md) (phase-gated, an owner on every item) → [`eol-internal-enablement`](skills/eol-internal-enablement/SKILL.md) (your teams ready *before* customers hear) → [`eol-message`](skills/eol-message/SKILL.md) (upgraded: three transition paths including the honest no-replacement case) → [`eol-process`](skills/eol-process/SKILL.md) (the whole thing, six phases, including the post-EOL review everybody skips)
  239. - **Right-sizing is a dial you set, not a verdict handed to you.** Every skill offers Light / Standard / Heavy, defaults to Standard, and names what a lighter choice leaves uncovered. A feature deprecation should never get a flagship playbook — that's how teams learn to ignore EOL process on the sunset that actually matters
  240. - **No tight coupling.** Every skill runs standalone; the workflow is a recommended route through independent stops, not a pipeline. Enter wherever you actually are — including mid-sunset, with a diagnostic that maps symptoms ("Support is drowning") to the phase that got skipped
  241. - Library now at **77 skills** · full story in the [release note](docs/announcements/2026-08-10-v0-84-lifecycle-and-eol-suite.md)
  242. **v0.83 — July 17, 2026 · The Market Intelligence Suite**
  243. - **14 new skills + 2 major upgrades** — the biggest single addition in the library's history. Run competitive and market research like an intelligence agency instead of a term paper: eight collection disciplines (OSINT → MASINT), signal → inference chains, confidence stacking, and a fusion cadence
  244. - New interaction mode: [`autonomous-investigation`](skills/autonomous-investigation/SKILL.md) — the protocol for research that proceeds *without* you. Question budgets, a search-plan gate, **Fact / Inference / Assumption** labels on every claim, do-not-invent lists, and stable diffable schemas, so investigations can run on a schedule and you can diff this quarter against last
  245. - The investigation chain ([market-landscape-scan](skills/market-landscape-scan/SKILL.md) → [competitive-research-snapshot](skills/competitive-research-snapshot/SKILL.md) → [competitive-intel-watch](skills/competitive-intel-watch/SKILL.md) → [battle-card-builder](skills/battle-card-builder/SKILL.md)), evidence-cited strategy frameworks ([swot-analysis](skills/swot-analysis/SKILL.md), [porters-five-forces](skills/porters-five-forces/SKILL.md), [ansoff-matrix](skills/ansoff-matrix/SKILL.md)), monitors and miners ([voice-of-customer-miner](skills/voice-of-customer-miner/SKILL.md), [pricing-packaging-tracker](skills/pricing-packaging-tracker/SKILL.md), [pestel-delta-monitor](skills/pestel-delta-monitor/SKILL.md)), and the six-step umbrella [competitive-analysis-process](skills/competitive-analysis-process/SKILL.md)
  246. - Upgraded: `tam-sam-som-calculator` (three entry modes, including autonomous bottom-up research) and `company-intel` (Executive Signal Refresh rerun pattern — Then/Now diffs and **Dropped Language**: what leaders *stop* saying is often the strongest signal)
  247. - Library now at **70 skills** · full story in the [release note](docs/announcements/2026-07-17-v0-83-market-intelligence-suite.md)
  248. **v0.82 — July 8, 2026**
  249. - Added `incoming-request-advisor` (Interactive) — drop in a Slack ping, email, mandate, or escalation and get a structured breakdown that separates the literal ask from the real job-to-be-done, reads sender power and stake, and points you toward a reply. Ships with a copy/paste template so you can run it by hand too
  250. - **New: a browsable [download shelf](dist/) at `/dist`** — no terminal, no Releases tab. Read the plain-language [README](dist/README.md), scan the [CATALOG](dist/CATALOG.md), and download any skill or pack straight from the repo. Built for PMs who just want the skills
  251. - Library now at **56 skills**
  252. **v0.81 — July 4, 2026**
  253. - Every skill now has a required `## Input` section: what to bring, what happens to context you supply up front (it's used, not re-asked), and reassurance that arriving empty-handed is fine — the guided flow covers the rest
  254. - Added `argument-hint` autocomplete for Claude Code users; deliberately **no** `$ARGUMENTS` templating — it breaks on every other runtime and teaches the reader nothing ([why](CONTRIBUTING.md))
  255. - Validator now enforces the convention: skills fail without an Input section or with bare `$ARGUMENTS` in the body
  256. - Streamlit playground shows each skill's "What to bring (all optional)" before you start a session
  257. - Restored `agent-orchestration-advisor` (Interactive) — the multi-agent workflow design skill was referenced everywhere but only existed on an orphaned commit; recovered from git history and brought up to current standards
  258. **v0.80 — June 19, 2026**
  259. - Added `stakeholder-identification` (Component) — comprehensive stakeholder brainstorm using allies/audiences/influencers, R/P/D marking, equity lens, and bias check; narrows to priority targets
  260. - Added `stakeholder-mapping` (Component) — two complementary grids (Power × Interest + Impact × Power); comparing outputs reveals who you're under-engaging relative to how much the product affects them
  261. - Added `stakeholder-engagement-advisor` (Interactive) — per-stakeholder engagement planning via Adaptive Decision Ladder: three questions on profile, power/impact, and context deliver tailored message framing, medium, cadence, and a named next action
  262. All three adapted from the [MITRE Innovation Toolkit](https://itk.mitre.org) via the companion repo [MITRE ITK Skills](https://github.com/deanpeters/MITRE-ITK-Skills) — worth a bookmark if you work in discovery, facilitation, or cross-functional product strategy.
  263. **v0.79 — May 15, 2026**
  264. - Added `organic-growth-advisor` — McKinsey Growth Pyramid triage for new segments, geographies, channels, or products
  265. - Added `pm-skill-creator` — interactive skill for designing repo-compliant skills via guided conversation
  266. - Fixed missing `.claude-plugin/plugin.json` that silently blocked Claude Code skill discovery
  267. - Added configurable input length guard (`PM_MAX_INPUT`) and path traversal protection to helper scripts
  268. → [Full changelog](docs/CHANGELOG.md)
  269. ---
  270. ## Contributing
  271. Found a gap? Have a PM framework worth formalizing? The bar is pedagogic — skills must teach the *why*, not just the *how*.
  272. See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines, or open an issue to start a conversation.
  273. ---
  274. ## License
  275. [CC BY-NC-SA 4.0](LICENSE) — non-commercial use with share-alike.
  276. **Everything in this repository — every skill, template, and doc — is licensed CC BY-NC-SA 4.0. There is no mix of licenses here.**
  277. Some skills note in their Provenance sections that they were adapted from [product-manager-prompts](https://github.com/deanpeters/product-manager-prompts), Dean's earlier prompt library. That repo has the same author, so there is no license conflict: a license grants permissions to *other* people, and a copyright holder is free to adapt and relicense their own work. Those Provenance lines are lineage — a breadcrumb back to where an idea started — not a license dependency. No third-party MIT-licensed text is incorporated anywhere in this library.
  278. **In plain terms:**
  279. - ✅ **Use these skills in your day job** — at a for-profit company, with your team, in your agents. That's what they're for.
  280. - ✅ **Adapt and remix them** — share what you build under this same license, with credit.
  281. - ✅ **Teach with them** — workshops, brown bags, mentoring, sending the ladder down.
  282. - ❌ **Don't sell them** — no repackaging the skills themselves into a paid product, course, or service without expressed written permission.
  283. - 📄 **Need something citable for your legal team?** See [LICENSING.md](LICENSING.md): internal use at a for-profit company is fine, and what you produce *using* the skills is yours.
  284. - 🤔 **Not sure your use qualifies?** [Open an issue](https://github.com/deanpeters/Product-Manager-Skills/issues) and ask. If you're using these in the spirit they were built — to get better at the craft and help others do the same — the answer is almost certainly yes.
  285. The companion prompt library, [product-manager-prompts](https://github.com/deanpeters/product-manager-prompts), carries the same CC BY-NC-SA 4.0 license as of its v2.3.0, with its own plain-language permissions (stricter on commercial use) — see its [LICENSING.md](https://github.com/deanpeters/product-manager-prompts/blob/main/LICENSING.md), which governs that repo.
  286. ---
  287. ## Questions
  288. - **GitHub Issues:** [Report bugs or suggest features](https://github.com/deanpeters/Product-Manager-Skills/issues)
  289. - **LinkedIn:** [Dean Peters](https://linkedin.com/in/deanpeters)
  290. - **Productside:** [AI PM consulting and training](https://productside.com)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.