October 2026 · 10 min read · 41 skills, free

Claude Docs for Product Managers: 41 Claude Skills to Write the Docs the Job Runs On

You set up once: your voice, your templates, a six-line brief. Then the documents of the product job in order — discovery, the canvases, the problem, the PRD, the memos, the strategy, the update, the launch, the review. The last skills cut what nobody will read.

01What these skills are

The documents of the product job, from the first brief to the post-launch review, as installable Claude skills

This is Claude for product documentation that starts from the reader and the decision, not the blank page: Claude drafts the document from your own sources, in your own voice, and you are the one who signs it.

The skills follow the documents in the order they come up, in ten stages. You set up once, and the last stage cuts what nobody will read.

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.

Each skill is one finished document you walk away with. It names its reader, holds a length budget, and ends with the decision a named person makes, by a date.

Each works from what you paste: the transcripts, this week's tickets, the metrics export, the figures finance gave you.

Each skill also says where the document lives: Claude Docs, a Google Doc from chat, or Claude for Word. When a surface is not on your plan, you get the same document as plain chat output.

The 41 are grouped into ten stages of the work, and each one gives full value on its own.

Download all 41 skills

One zip: ready-to-install skill zips, readable SKILL.md files, and the notes naming the source behind every method. Free, no signup. The same 41 skills live in our open repo, if you would rather read them before you install them.

Download the zip Browse on GitHub

Install in Claude Code

Two lines, and every skill in the pack loads at once.

/plugin marketplace add polar-bear-org/claude-skills
/plugin install docs-for-product-managers-pack@polar-bear-skills

Using Claude on the web instead? Download the zip above and upload each skill from its install folder under Customize → Skills.

02The catalog

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

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

03How to use it

Pick the workflow that matches your week

No fixed order. Bring one document you owe somebody and open the skill that matches it. The three set-up skills are worth running first.

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

04Setup guide

Install it in five minutes

In Claude Code · two lines

/plugin marketplace add polar-bear-org/claude-skills
/plugin install docs-for-product-managers-pack@polar-bear-skills

In Claude.ai or Claude Desktop · seven clicks

Download the pack, then open Settings
Unzip the pack: its skills folder holds all 41 skills. In Claude, click your name at the bottom left, then Settings.
Download the zip
Open Skills and click Add
Under Customize, choose Skills. Click Add, then Upload a skill.
Drop in a skill file
Drag the skill's file into the box, or click to browse. You can add several at once.
Pick the skill from the pack
In the pack folder, open skills, then the skill you want, and select its SKILL.md — doc-writing-style-guide is a good first one.
Check the preview and upload
Claude shows the skill's name and what it does. Click Upload.
Make sure it is switched on
The skill opens on its own page. Its toggle should be on.
Try it in a new chat
Type / and the skill's name, then say what you need.

Then try one

Run doc-writing-style-guide on three to five documents I wrote myself: [paste them here]

Run doc-prd for [feature]. My sources: [paste the transcripts, tickets or metrics here]

Run doc-plain-language-edit on this document: [paste it here]

Lantern for product managers

Turn the docs you already wrote into posts people read

Lantern drafts a week of posts from your notes and call transcripts, in your voice. You review them and publish the ones you like.

100 free credits, about ten posts. No card needed.

Try for free

05Quick reference

Where to start

Your situation	Skill to run
Need docs that sound like you, not like AI?	Writing Style Guide
Need Claude to keep your company template?	Doc Template Kit
Need the reader and the length fixed before writing?	Doc Brief
Need research notes turned into findings?	User Research Summary
Need the why written before the demo wins?	Problem Statement
Need a spec everyone reads the same way?	PRD
Need a no that holds?	Trade-off Memo
Need a decision that stays made?	Decision Memo
Need a roadmap without false dates?	Roadmap Narrative
Need an update people act on?	Weekly Product Update
Need every team ready on launch day?	Product Launch Plan
Need the bottom line on top?	Executive Summary

06Standards

The quality bar

Every skill in the pack holds the same standard, the one we hold for the documents we write ourselves:

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

07FAQ

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.

08Who made this

Lantern, by Polar Bear

These skills were written by Polar Bear, a people ops consultancy that runs its own company on Claude. The pack is free, and the same skills are open on GitHub.

Lantern is Polar Bear's content workspace. It turns your notes, documents and call transcripts into drafts for LinkedIn and other networks. You review them and publish the ones you like.