claude

docs-for-product-managers-pack

41 skills for the documents product people write, from the first brief to the post-launch review: setting up your voice and templates, discovering, shaping the vision, defining the work, deciding, aligning, reporting up, shipping and learning, running the team, and reviewing and editing. Each skill produces one finished document with a named reader and a length budget.

54 on GitHubby 90nv1.0.0LicenseRef-PolarBear-Internal-Useupdated 17 days agoproductivity
/

Plugin docs-for-product-managers-pack from marketplace 90n-skills in polar-bear-org/claude-skills. Commands read from the repo's manifest — 17 days ago.

What it installs

Skills (41)

  • doc-ai-feature-spec

    Writes an AI Feature Spec and Eval Plan covering the inputs the model sees, its outputs, must and must-never behaviour, failure handling, measurable success criteria, a starting set of real test cases and who reads transcripts when. Use for "run doc-ai-feature-spec", "spec an AI feature", "eval plan

  • doc-board-memo

    Writes a Board Memo, Product Section with the questions for the board first, progress against plan, the few metrics that matter with base and period, and risks with what is being done, in one or two pages. Use for "run doc-board-memo", "product section of the board pack", "board memo for product", "

  • doc-brief

    Writes a six-line doc brief (purpose, reader, decision wanted, length budget, sources to use, what to leave out) that goes at the top of any document request. Use for "run doc-brief", "brief before I write", "who is this doc for", "how long should this doc be", "set up this doc", "brief for my PRD",

  • doc-business-case

    Writes a Business Case with the case for change, options including do nothing, costs and benefits as ranges with named assumptions, affordability, a delivery plan and the ask. Use for "run doc-business-case", "write the business case", "finance wants an ROI", "make the numbers hold up", "funding req

  • doc-business-model-canvas

    Maps the nine Business Model Canvas blocks in Claude Docs (beta) for today and for the bet if it works, lists what changes for the business and who owns each change, and marks every block tested or untested. Use for "run doc-business-model-canvas", "business model canvas", "what changes for the busi

  • doc-competitive-analysis

    Builds a competitive analysis with a comparison table by customer need where every cell carries a source and a checked-on date, where we win and lose, a five forces check and what we will not copy. Use for "run doc-competitive-analysis", "competitive analysis", "competitor landscape", "a competitor

  • doc-decision-log

    Keeps a Decision Log as a dated table of short records with context, options considered, decision, decider, status, consequences and a link to the memo or notes, superseding old entries instead of editing them. Use for "run doc-decision-log", "log this decision", "decision log", "why did we decide t

  • doc-decision-memo

    Writes a Decision Memo with the question in one line, options with evidence, a recommendation, a reversibility call, who decides by when and a signature line. Use for "run doc-decision-memo", "write the decision memo", "get sign-off that sticks", "we keep reopening this decision", "lay out the optio

  • doc-executive-summary

    Writes an executive summary for the top of any long doc, with the answer in one line, three supporting points and the ask, under 120 words and counted. Use for "run doc-executive-summary", "write an exec summary", "bottom line up front", "summarise this for leadership", "TL;DR for my boss", "my doc

  • doc-experiment-readout

    Writes an Experiment Readout with the hypothesis, design, sample and duration, the result with its interval, guardrail metrics, the decision and what we learned. Use for "run doc-experiment-readout", "experiment readout", "write up the A/B test", "did the test win", "the result is not significant",

  • doc-handover

    Compiles a Handover Doc with the state of each workstream, a register of open decisions and risks, key people by role, where things live and the first two weeks for the next owner. Use for "run doc-handover", "handover doc", "I am going on leave", "changing teams", "hand over my workstreams", "I too

  • doc-interview-guide

    Writes a customer interview guide that fits your slot, with research questions, a behaviour-based screener, story-based questions with probes and a note sheet. Use for "run doc-interview-guide", "customer interview guide", "interview questions for users", "prep my customer call", "discovery intervie

  • doc-launch-plan

    Writes a Product Launch Plan with a launch tier, the audiences, a readiness checklist by team with dates and owners, go or no-go criteria and a comms list. Use for "run doc-launch-plan", "launch plan", "launch checklist", "what tier is this launch", "support heard about it from customers", "launch r

  • doc-lean-canvas

    Fills a one-page Lean Canvas in Claude Docs (beta) with problem, segments, unique value proposition, solution, channels, revenue, costs, key metrics and unfair advantage, every statement marked tested or untested, plus the riskiest assumptions with the cheapest test for each. Use for "run doc-lean-c

  • doc-meeting-notes

    Turns a transcript or rough notes into a Meeting Record of decisions with who decided, actions with one owner and a date, and open questions with who answers, plus a same-day send line for corrections. Use for "run doc-meeting-notes", "write up this meeting", "meeting notes from this transcript", "w

  • doc-metrics-review

    Writes a Weekly Metrics Review with input and output metrics carrying base and period, what moved and the likely reason, the actions with owners and the questions for metric owners. Use for "run doc-metrics-review", "write up the weekly metrics", "what does the dashboard mean this week", "metrics re

  • doc-okrs

    Writes Product OKRs for the quarter with one to three objectives, outcome key results with baselines and sources, a what we stop doing list and the check-in rhythm, plus end-of-quarter grading of key results only. Use for "run doc-okrs", "write our product OKRs", "quarterly planning", "our OKRs read

  • doc-onboarding

    Builds a PM Onboarding Guide covering the product, users, strategy, metrics, who is who by role, how decisions get made, open threads and a first 30 days of learning goals, linking to existing docs rather than copying them. Use for "run doc-onboarding", "onboarding doc for a new PM", "a new PM joins

  • doc-one-pager

    Writes a Pitch One-Pager with the problem, the appetite, a rough proposed approach, rabbit holes, no-gos and open questions, on one page for a named decider. Use for "run doc-one-pager", "write a one-pager", "pitch this bet", "shape up pitch", "I need a yes before the spec", "appetite and no-gos", "

  • doc-opportunity-assessment

    Writes a one-page Opportunity Assessment in Claude Docs (beta) with the ten standard opportunity questions answered from your sources, the riskiest unknowns ranked, and a go / not now / no recommendation for a named person. Use for "run doc-opportunity-assessment", "opportunity assessment", "should

  • doc-plain-language-edit

    Edits one document into plain language, returning a shorter version with word counts before and after, AI tells removed, and every edit listed so you can reject it, with every fact and number unchanged. Use for "run doc-plain-language-edit", "make this sound less like AI", "cut this doc in half", "r

  • doc-post-launch-review

    Writes a Post-Launch Review with goals against actuals and their sources, adoption reported apart from engagement, what surprised us, and a keep, change and stop list with owners. Use for "run doc-post-launch-review", "post-launch review", "did the launch work", "launch retrospective", "customers st

  • doc-pr-faq

    Writes a Working Backwards PR/FAQ with a one-page launch-day press release, an external FAQ and an internal FAQ that asks the hard questions. Use for "run doc-pr-faq", "write a PR/FAQ", "working backwards doc", "press release before we build", "prove customers care", "why are we building this", "int

  • doc-prd

    Writes a Product Requirements document with the problem, goals and non-goals, users, prioritised requirements, edge cases, open questions and success metrics, each section held to a length budget, with a summary tab and a detail tab. Use for "run doc-prd", "write a PRD", "spec this feature", "produc

  • doc-problem-statement

    Writes a Problem Statement naming who has the problem and in what situation, the evidence and cost behind it, what success looks like, and one "how might we" line. Use for "run doc-problem-statement", "write the problem statement", "what problem are we solving", "leadership saw a demo and wants it s

  • doc-product-strategy

    Writes a Product Strategy doc with a diagnosis of the critical challenge, a guiding policy that rules things out, three to five coherent actions, a what we will not do list and the signals that show it is working. Use for "run doc-product-strategy", "write our product strategy", "everything is high

  • doc-qbr

    Writes a Quarterly Business Review Doc with the answer and asks on top, key results graded against results with base and period, shipped against promised, lessons and next quarter's bets. Use for "run doc-qbr", "write the QBR", "quarterly business review doc", "grade our key results", "quarter revie

  • doc-release-notes

    Writes Release Notes for customers grouped Added, Changed, Fixed and Removed with the benefit first, plus an internal version for support with ticket links and known issues. Use for "run doc-release-notes", "release notes", "write the changelog", "what's new post", "turn these tickets into release n

  • doc-research-summary

    Turns interview notes and transcripts into a user research summary with a one-paragraph top line, findings with session counts and sources, what we still do not know, and opportunities under your outcome. Use for "run doc-research-summary", "summarise these interviews", "research findings doc", "aff

  • doc-rfc-review

    Reviews an RFC or design doc against your PRD and returns review comments by severity, the edge cases and missing requirements, questions for the author, and a go, revise or discuss call for the named approver. Use for "run doc-rfc-review", "review this RFC", "review this design doc", "is this spec

  • doc-roadmap-narrative

    Writes a Roadmap Narrative in prose, with Now, Next and Later items stated as problems, the strategy action behind each, confidence per horizon and what changed since last time and why. Use for "run doc-roadmap-narrative", "write our roadmap as a doc", "now next later roadmap", "roadmap without date

  • doc-roadmap-review-pre-read

    Writes a Roadmap Review Pre-Read with the decision asked at the top, what changed since last time and why, Now, Next and Later with confidence, and what is not on the roadmap and why. Use for "run doc-roadmap-review-pre-read", "pre-read for the roadmap review", "roadmap review memo", "we keep explai

  • doc-sales-enablement-brief

    Writes a Sales Enablement Brief with who the feature is for, the problem it solves in customer words, what it does not do, objections with answers and an internal FAQ. Use for "run doc-sales-enablement-brief", "sales enablement brief", "brief the sales team", "sales promised it before it shipped", "

  • doc-sunset-notice

    Writes a Feature Sunset Notice with the internal decision note and the customer notice covering what is going, why, when, what replaces it, migration steps and a support FAQ. Use for "run doc-sunset-notice", "sunset notice", "deprecate a feature", "retire a feature customers still use", "deprecation

  • doc-team-charter

    Drafts a Team Charter with mission, customers, scope and not-scope, roles with primary and backup owners, decision rights by decision type, working agreements and a review date. Use for "run doc-team-charter", "team charter", "nobody knows who decides", "new product team kickoff", "working agreement

  • doc-template-kit

    Turns your team's PRD, memo and update templates into a reusable kit of outlines with a rule per section and a filled sample for each, so Claude keeps your headings. Use for "run doc-template-kit", "Claude ignores our template", "use our PRD template", "turn our templates into a kit", "keep our head

  • doc-trade-off-memo

    Writes a Trade-off Memo that sets one incoming request against the work it would displace, with the cost of delay of each, a recommendation and the costed no reply ready for you to send. Use for "run doc-trade-off-memo", "why we are not building it", "help me say no to this request", "what would thi

  • doc-user-stories

    Writes a Story Set from a PRD section, with stories in "As a, I want, so that" form, Given / When / Then acceptance criteria, an INVEST check per story and questions for refinement. Use for "run doc-user-stories", "write user stories", "acceptance criteria", "Given When Then", "INVEST check", "break

  • doc-value-proposition-canvas

    Fills a Value Proposition Canvas in Claude Docs (beta) with customer jobs, pains and gains from your research, a value map linked to them, fit notes, and one positioning line every team uses. Use for "run doc-value-proposition-canvas", "value proposition canvas", "jobs pains and gains", "sales and m

  • doc-weekly-update

    Writes a Weekly Product Update under 250 words, with the decision or help needed at the top, what changed, risks with evidence and owners, what is next and links, drafted from your connected tools. Use for "run doc-weekly-update", "write my weekly update", "Friday status update", "weekly product upd

  • doc-writing-style-guide

    Builds a one-page voice and style guide from three to five of your own documents, with a banned words and phrases list and length defaults per doc type, saved once to a Project or memory. Use for "run doc-writing-style-guide", "make Claude write like me", "my docs sound like AI", "build a style guid

View source on GitHub 90n.ai

More from polar-bear-org/claude-skills

All 38 plugins →

42 skills for the whole product job, stage by stage, from the vision to the weekly update, in eight stages: set direction, discover, decide, define, deliver, launch, prove, and run the product. Each skill is named as an action and keeps one framework inside, with the inputs it needs, where it breaks, a fixed output template, a finish line and the next skill to run.

42 skills

54

The Complete Claude Guide for L&D: 40 Claude skills for the whole L&D job, in eight stages: diagnose the need with the request triage, the performance gap and the action map; work with the experts through the interview, the task breakdown and the review plan; design the learning with objectives, an evaluation plan, a design document and a curriculum map; build and test scenarios, a storyboard, a knowledge check, the check of an AI draft and a learner walkthrough; run the room with a session plan, slides, a facilitator guide and a pilot; carry it into work with a job aid, spaced practice and a manager briefing; measure what changed with a feedback form, an ROI estimate and the one-page report; and lead L&D through the year plan and the business case. For L&D managers and specialists, instructional designers, trainers and facilitators, and L&D leaders. Claude drafts and checks, people decide: nothing a learner does in training is used to grade, rank or build a case against them.

40 skills

54

Claude for Consultants · Team in Claude: 39 Claude skills for winning and shaping client work when the client has AI too, from their brief to the signed scope, as eight desks in order: Intake reads the client's brief, qualifies the opportunity and records the bid or no-bid decision; Discovery prepares the call, keeps the notes and sends the recap email; Problem writes the problem statement, the issue tree and the hypothesis test plan; Strategy builds options and the recommendation memo; Pricing shapes good-better-best options, fees and a MoSCoW scope; Proposal writes the consulting proposal, the AI use statement and the statement of work; the Client room prepares the walk-through deck, the AI objection answer and the negotiation plan; Follow-through covers follow-up emails, the mutual action plan and the win/loss review. For independent consultants and partners in advisory practices. Claude structures, drafts and checks; it never invents a reference, a result, a number or a client quote, and you run the conversation, make the recommendation and send everything yourself.

39 skills

54

39 skills for running the whole product cycle with Claude, in seven phases that each hand a named artifact to the next: set Claude up and connect it, frame the question, discover the evidence, decide, build and ship, communicate the call and run the week. Each skill teaches one named, checkable method, with the inputs it needs, where it breaks, a fixed output template and the next skill to run.

39 skills

54

36 skills for deciding if AI fits, testing it before launch and keeping it honest after: deciding if AI fits, speccing it as tests, briefing the model and the agent, building the evals from real outputs, shipping it safely, running and improving it, and its cost, price and explanation to leaders. Each skill is one named method or one artifact, with the inputs it needs, where it breaks and a fixed output template.

36 skills

54

33 Claude Skills that carry a design project from a fuzzy challenge to a tested, decision-ready concept: challenge framing, interview guides and screeners, transcript synthesis, personas and journeys, HMWs and concept cards, prototype and test plans, and the stakeholder playback.

33 skills

54

Similar plugins

caveman

claude

Talk like caveman. Cut filler. Keep technical details explicit.

22 skills · 1 command · 3 agents · hooks

JuliusBrussee/caveman 119,462

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

pake

claudecodex

Package any website or local web build into a lightweight desktop app with Pake CLI.

1 skill

tw93/Pake 63,463

Maintain docs-for-product-managers-pack?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins38 plugins