7 Claude Skills for Product Managers That Handle the Documentation Work

Product management runs on written artefacts. Specs, briefs, roadmap updates, metrics reviews, competitive analysis, stakeholder communications — the work is roughly half thinking, half documentation. The thinking is what PMs get paid for. The documentation takes longer than it should.

Agent Skills give Claude a structured template for each of these outputs so you spend less time formatting and more time on the work that actually requires your judgment. Install a skill once, and Claude produces that deliverable the same way every time — in the format your engineering team, your stakeholders, and your leadership expect — without you having to re-explain the structure on every session.

The seven skills below are built from Anthropic’s official product management plugins. They cover the core PM workflow from spec writing and sprint planning through to metrics review and board-level communication. They work with Claude Code and Claude.ai — whichever fits your existing setup.

The skills

1. Product Management Write Spec

A good spec has a specific structure: background and context, problem statement, requirements (functional and non-functional), acceptance criteria, edge cases and exclusions, open questions, and the success metrics that define done. Writing that from scratch every time — even when you know exactly what you want to build — is slower than it should be.

The Product Management Write Spec skill gives Claude a structured approach to writing product specs from a feature brief, user story, or rough idea. It produces requirements in a format engineering teams can actually use: acceptance criteria that are testable, edge cases that are explicit, and open questions that are surfaced rather than buried.

Use it when you have a clear idea of what to build and need to translate it into a spec quickly, when you’re writing specs for a sprint and need consistent format across all stories, or when a feature request from a stakeholder needs to be formalised into something the team can scope and estimate.

npx skills add anthropics/knowledge-work-plugins --skill product-management

---

2. Product Management Sprint Planning

Sprint planning is one of those meetings that takes longer than it should and produces inconsistent output depending on who’s running it. The capacity calculation is manual, the prioritisation logic isn’t always explicit, and the stories don’t always get broken down into pieces the team can actually complete in a sprint.

The Product Management Sprint Planning skill gives Claude a structured approach to sprint planning: capacity calculation based on team size and availability, backlog prioritisation using structured criteria, story breakdown for items that are too large, and a final sprint plan with priorities flagged for discussion.

Use it at the start of every sprint cycle — input your backlog items and team capacity, get a structured plan you can walk into the sprint planning meeting with. Cuts the prep time and makes the conversation more productive because the structure is already in place before the meeting starts.

npx skills add anthropics/knowledge-work-plugins --skill product-management

---

3. Product Management Roadmap Update

Roadmap communications have a clarity problem. Working notes have the right information but wrong format. Executive summaries lose the necessary detail. The version that goes to engineering is different from the version that goes to sales is different from the version that goes to the board — and maintaining all of them is more work than it sounds.

The Product Management Roadmap Update skill gives Claude a structured approach to producing roadmap updates for stakeholders: what’s in progress, what’s planned and on what timeline, what’s changed since last time and why, and what decisions or inputs are needed from the audience. It produces a version that’s structured for presentation rather than just accurate.

Use it before quarterly business reviews, before leadership check-ins on the product direction, or whenever your working roadmap notes need to become a shareable document. Input your current initiatives and priorities; get a formatted update ready to send.

npx skills add anthropics/knowledge-work-plugins --skill product-management

---

4. Product Management Metrics Review

Metrics reviews have two failure modes. The first is descriptive without being actionable — here are the numbers, they went up or down. The second is actionable without proper analysis — here are the things we should do, with no clear connection to what the data actually shows. The useful version requires trend analysis, diagnosis, and a clear link between observation and recommendation.

The Product Management Metrics Review skill gives Claude a structured approach to analysing product metrics: trend analysis across key indicators (activation, retention, engagement, conversion), diagnosis of meaningful changes versus noise, identification of leading indicators and lagging outcomes, and recommended actions with clear rationale.

Use it when running a weekly, monthly, or quarterly metrics review — input the numbers and the context, get a structured scorecard with observations and recommended actions. Also useful when presenting metrics to leadership or a board and you need the narrative to be structured rather than just a slide of charts.

npx skills add anthropics/knowledge-work-plugins --skill product-management

---

5. Product Management Competitive Brief

Competitive analysis for product purposes is different from competitive analysis for sales. The product version asks: how do competitors approach this problem, what decisions have they made about the feature set, what are the trade-offs in their approach, and what does that tell us about our own product direction? Sales decks compare features. Product briefs analyse decisions.

The Product Management Competitive Brief skill gives Claude a structured approach to competitive analysis: how competitors position and package a specific feature area, the trade-offs implicit in their implementation decisions, what their approach reveals about their product strategy, and the implications for your own roadmap prioritisation.

Use it when evaluating a feature area before committing to a design direction, when preparing competitive context for a board presentation, or when a sales or marketing request for competitive information needs to be translated into a product-useful format.

npx skills add anthropics/knowledge-work-plugins --skill product-management

---

6. Product Management Stakeholder Update

Stakeholder updates have a specific job: give the right audience the right level of detail, surface the blockers and decisions they need to care about, and do it without burying the important things in operational detail. Most PMs write stakeholder updates that are either too detailed (an internal status report) or too thin (a one-paragraph summary that doesn’t tell the audience anything actionable).

The Product Management Stakeholder Update skill gives Claude a structured approach to drafting stakeholder updates: progress against commitments, current blockers and their impact, decisions the stakeholder needs to make or approve, and what’s coming next. The structure is adapted for the audience — engineering updates look different from board updates.

Use it before leadership reviews, investor product updates, cross-functional check-ins, or any communication where stakeholders need a clear picture of where the product is and what they need to do. Input your current situation and the audience; get a structured update ready to review and send.

npx skills add anthropics/knowledge-work-plugins --skill product-management

---

7. CPO Advisor

Most product decisions get made at the feature level. The harder questions — what problem is the product actually solving, is the current roadmap coherent with the product strategy, is there a PMF issue underneath the engagement metrics — require a different frame. One that most PMs don’t get from their manager, their team, or their peers.

The CPO Advisor skill gives Claude a structured Chief Product Officer perspective on the hardest product questions: product vision and strategy, portfolio trade-offs, PMF diagnosis, roadmap governance, and the framework for making calls that aren’t resolvable by looking at the data alone.

Use it when making a major prioritisation call that doesn’t have a clear right answer, when diagnosing a PMF issue that isn’t showing up cleanly in the metrics, or when preparing for a board or leadership discussion about product direction and you want structured preparation. Works best as a thinking partner rather than a one-shot prompt.

npx skills add alirezarezvani/claude-skills --skill c-level-advisor/cpo-advisor

---

How these skills chain together

Here’s how these skills fit into a typical PM workflow — from strategy through delivery to communication.

Strategy layer: Use CPO Advisor when working through major product direction decisions — what to build, what to cut, where the PMF gaps are. Use Competitive Brief to add market context before committing to a direction.

Planning layer: Use Write Spec to turn approved feature work into implementation-ready specs. Use Sprint Planning to translate the backlog into a structured sprint plan each cycle.

Review layer: Use Metrics Review weekly or monthly to track outcomes and generate recommendations. Use this to feed the Roadmap Update — what changed, what it means, what’s shifting.

Communication layer: Use Stakeholder Update before every leadership or cross-functional touchpoint. Use Roadmap Update before quarterly planning sessions, board meetings, or any external review of the product direction.

---

How to install

New to Agent Skills? Install with one command in your terminal, or download the files and paste them into Claude.ai Project Instructions.

→ Full install guide

Browse all product manager skills → /audiences/product