# Claude Docs for Product Managers: 41 Claude Skills to Write the Docs the Job Runs On From the first brief to the post-launch review — 41 skills that draft each product document from your own sources, with a named reader, a length budget and nothing invented. - Page: https://lantern.meet-polar-bear.com/skills/docs-for-product-managers-pack - Download: https://lantern.meet-polar-bear.com/skills/docs-for-product-managers-pack.zip - Source: https://github.com/polar-bear-org/claude-skills/tree/main/packs/docs-for-product-managers-pack - Price: free ## Install in Claude Code ``` /plugin marketplace add polar-bear-org/claude-skills /plugin install docs-for-product-managers-pack@polar-bear-skills ``` ## The 41 skills you get The set follows the documents, in ten stages: the set-up that runs once, discovery, shaping the vision, defining the work, deciding, aligning, reporting up, shipping and learning, running the team, and the pass over what is already written. ### 1 · Set up once - **Writing Style Guide** — use when: Everything Claude writes sounds like AI, and your team can tell. Output: One-page voice guide from your own docs, banned words list, length defaults per doc type. - **Doc Template Kit** — use when: AI ignores your template and invents its own headings. Output: Your PRD, memo and update templates as reusable outlines, section rules, a filled sample. - **Doc Brief** — use when: Before any doc, so it is the length people will read. Output: Purpose, reader, decision wanted, length budget, sources, what to leave out, in six lines. ### 2 · Discover - **Customer Interview Guide** — use when: You get 30 minutes with a customer, once. Output: Research questions, screener, story-based questions, note sheet. - **User Research Summary** — use when: Notes and transcripts pile up and nobody reads them. Output: Findings with counts and sources, what we still do not know, opportunities, top line. - **Competitive Analysis** — use when: A competitor launches and it lands on the roadmap by Monday. Output: Comparison table with dated sources, where we win and lose, what we will not copy. ### 3 · Shape the vision - **Opportunity Assessment** — use when: An idea arrives and needs one page before anyone commits a team. Output: One page on the standard opportunity questions, riskiest unknowns, go or not now. - **Lean Canvas** — use when: A new bet needs its business logic on one page. Output: One-page canvas with the riskiest assumptions marked untested. - **Business Model Canvas** — use when: The feature changes how the business makes money, sells or delivers. Output: The nine blocks, what changes for the business, untested assumptions. - **Value Proposition Canvas** — use when: Marketing, sales and product each describe the product differently. Output: Jobs, pains and gains from research, value map, fit notes, one positioning line. ### 4 · Define - **Problem Statement** — use when: Leadership saw a demo and wants it shipped before anyone asks why. Output: Who, situation, evidence, cost of the problem, success, a “how might we” line. - **Product One-Pager** — use when: A bet needs a yes before anyone writes a full spec. Output: Problem, appetite, approach, rabbit holes, no-gos, open questions on one page. - **PRD (Product Requirements Document)** — use when: A long spec was read differently by everyone. Output: Goals and non-goals, users, prioritised requirements, edge cases, metrics, length budget. - **AI Feature Spec and Eval Plan** — use when: Nobody can say how anyone will test what good means for an AI feature. Output: Model inputs and outputs, must and must-never behaviour, success criteria, test cases. - **User Stories and Acceptance Criteria** — use when: Engineers say the requirements are not detailed enough. Output: Stories, Given/When/Then criteria, INVEST check, refinement questions. ### 5 · Decide - **Trade-off Memo** — use when: You must write why you are not building it, then defend it. Output: The request, what it displaces, cost of delay of each, recommendation, the costed no. - **Decision Memo** — use when: Sign-off happens, then people change their minds. Output: Options with evidence, recommendation, reversibility, who decides by when, signature line. - **Working Backwards PR/FAQ** — use when: A big feature has to prove customers care before engineering starts. Output: One-page press release, external FAQ, internal FAQ with the hard questions. - **Business Case** — use when: Finance will pick apart any ROI projection. Output: Case for change, options including do nothing, ranges with named assumptions, the ask. ### 6 · Align - **Product Strategy** — use when: A leader says everything is high priority. Output: Diagnosis, guiding policy, coherent actions, what we will not do. - **Roadmap Narrative** — use when: A date on the roadmap becomes a promise. Output: Written Now, Next, Later with the problem behind each item, confidence, what changed. - **Product OKRs** — use when: Quarterly planning, or OKRs that read like task lists. Output: 1 to 3 objectives, outcome key results with baselines, what we stop, check-in rhythm. - **Weekly Product Update** — use when: Friday afternoons on a report people skim in seconds. Output: Decision needed at the top, what changed, risks with evidence, what is next, under 250 words. ### 7 · Report up - **Weekly Metrics Review** — use when: The dashboard exists and nobody writes down what it means. Output: Input and output metrics with base and period, what moved and why, actions, owner questions. - **Roadmap Review Pre-Read** — use when: The roadmap review is spent explaining instead of deciding. Output: What changed, now-next-later with confidence, what is off and why, the decision asked. - **Quarterly Business Review Doc** — use when: The quarter ends and leadership wants the review written first. Output: Goals against results, shipped against promised, lessons, next bets, the asks. - **Board Memo, Product Section** — use when: The CEO needs the product section of the board pack by Friday. Output: Progress against plan, the few metrics that matter, risks, the question for the board. ### 8 · Ship and learn - **Product Launch Plan** — use when: Support hears about a feature from customers. Output: Launch tier, readiness checklist by team, dates and owners, go or no-go criteria, comms list. - **Sales Enablement Brief** — use when: Sales promised it before it shipped, or cannot explain it after. Output: Who it is for, the problem in customer words, what it does not do, objections, internal FAQ. - **Release Notes** — use when: Every release, or a changelog nobody reads. Output: Customer notes grouped Added, Changed, Fixed, Removed, benefit first, plus an internal version. - **Feature Sunset Notice** — use when: You have to retire a feature customers still use. Output: Internal decision note, customer notice, dates, replacement, migration steps, support FAQ. - **Experiment Readout** — use when: An A/B test ends and is read as the answer it hoped for. Output: Hypothesis, design, sample, result with interval, guardrails, decision, lessons. - **Post-Launch Review** — use when: Customers still use the old workflow two weeks after launch. Output: Goals against actuals with sources, adoption, surprises, keep, change, stop, owners. ### 9 · Run the team - **Meeting Notes and Decisions** — use when: Every review someone disputes what was decided last time. Output: Decisions, actions with owners and dates, open questions, sent the same day. - **Decision Log** — use when: Decisions get reopened because nobody can find why. Output: Dated table of decisions with context, options, decider, status, link. - **Team Charter** — use when: A new team forms, or nobody knows who decides. Output: Mission, customers, scope, roles, decision rights, working agreements, review date. - **Handover Doc** — use when: You change teams, go on leave or take over mid-way. Output: State of each workstream, open decisions, risks, key roles, first two weeks. - **New PM Onboarding Doc** — use when: A new PM would otherwise learn the product from chat scrollback. Output: Product, users, strategy, metrics, who decides what, open threads, first 30 days. ### 10 · Review and edit - **RFC and Design Doc Review** — use when: A 30-page RFC lands, or a polished spec misses an edge case. Output: Comments by severity, edge cases, missing requirements, questions, a go, revise or discuss call. - **Executive Summary** — use when: Execs want the bottom line first and your doc buries it. Output: The answer in one line, three supporting points, the ask, under 120 words. - **Plain Language Edit** — use when: Eight paragraphs could have been one sentence. Output: Shorter version, word count before and after, AI tells removed, edits listed. ## Workflows - **Set up once** (Before the first document, so every later one is in your voice and at the right length.) Writing Style Guide → Doc Template Kit → Doc Brief - **From interviews to the problem** (You have customer conversations to run, or to write up.) Customer Interview Guide → User Research Summary → Problem Statement → Opportunity Assessment - **Win the yes, then spec it** (The PRD is due Thursday.) Product One-Pager → PRD (Product Requirements Document) → User Stories and Acceptance Criteria - **Settle what gets built** (The memo has to say no to the feature the CEO wants this quarter.) Trade-off Memo → Decision Memo → Decision Log - **Align the company** (The answer has to sit where the company can see it.) Product Strategy → Roadmap Narrative → Product OKRs - **Report up** (The Friday update, and everything that carries it upward.) Weekly Product Update → Weekly Metrics Review → Quarterly Business Review Doc → Board Memo, Product Section - **Ship and learn** (A launch is going out, and you want to know what it changed.) Product Launch Plan → Sales Enablement Brief → Release Notes → Experiment Readout → Post-Launch Review ## The quality bar - One document, one method: each skill runs the real mechanics of a named method or artifact — its sections, its grid, its formula, the order of the pass — not a generic gather, analyse, recommend - Every document names who reads it and how long it may be, and the answer or the decision sits at the top - Every skill says when not to use it, and which skill fits instead - The same shape every time: a fixed output template, a short done-when check before handover, and the next skill to run - No invented numbers: a figure, a quote or a date you have not given stays a [placeholder] until you set it - Work is reviewed, people are not: the skills assess options, requirements, risks, metrics and documents, never colleagues or individual customers - The red line: Claude drafts from your sources, in your voice, at the length the reader will actually read; it never invents a number, a quote or a decision, and a named person signs every decision a doc records ## Questions people ask ### What is in the Claude Docs for Product Managers pack? 41 Claude skills for the documents of the product job, in ten stages from set-up to review and edit. Each skill produces one finished document that names its reader, holds a length budget and ends with the decision a named person makes. ### How do I install these Claude skills? In Claude Code, two lines install all 41 at once. In Claude.ai or Claude Desktop, download the zip, open Settings, Skills, Add, and upload the skills you want. Either way it takes about five minutes. ### Do I need Claude Code to use them? No. The skills work in Claude.ai, Claude Desktop and Claude Code. In the app you upload them yourself; in Claude Code one command installs the whole pack. ### Do the skills work with ChatGPT or other assistants? They are built as Claude Skills, and installing them is a Claude feature. Each one is a plain Markdown file, so you can read it and reuse the method elsewhere, but it will not load and trigger by itself outside Claude. ### Will Claude make the decisions my docs record? No. Claude drafts from your sources, in your voice, at the length the reader will actually read. It never invents a number, a quote or a decision, and a named person signs every decision a doc records. ### Is the pack free? Yes. It is free to use inside your company and in client work, and not for resale. There is no signup: the download and the install command are on this page. ## About Written by Polar Bear (https://meet-polar-bear.com/). Published on Lantern (https://lantern.meet-polar-bear.com/), which turns your notes, documents and call transcripts into social post drafts you review and publish.