Practical AI skills for Business & Product Management

Ten Claude Code skills a product team will actually use

Product work is mostly a loop. Someone has an idea, someone talks to customers, a spec gets written, priorities shift, a sprint starts, numbers come in, and then everyone needs an update. These ten skills map onto that loop, so they're listed in the order you'd meet them during a normal cycle rather than ranked against each other.

Each one is written as a user story, followed by what the skill does and a prompt to try. I checked the skill descriptions and instructions before writing this, so the details are accurate. The scenarios are made up.

1. /brainstorm

As a PM with an idea I haven't tested, I want something that asks hard questions before I commit, so I find the holes before my team does.

This one is built to disagree with you. If you say "what if we added a marketplace," it's more likely to ask who has this problem today and what they do about it now than to start listing features. It can work on the problem itself, generate a batch of options, or stress-test one you've already picked, and it brings in frameworks like How Might We and Jobs to be Done when they help.

It's a conversation, not a document generator, so don't expect a deliverable at the end. There's also a product-brainstorming skill that covers the same ground and can be picked up automatically when the topic comes up.

Try: /brainstorm why do new users drop off after day three?

2. /synthesize-research

As a researcher, or a PM who ended up doing research, I want to feed in a pile of interview notes, survey answers, and support tickets and get back themes ranked by frequency and impact, so I can show what customers said without rereading everything.

You paste in or upload what you have. It pulls out observations, quotes, and pain points from each source, groups them into themes, and sorts them into a priority matrix: common and painful at the top, rare and mild at the bottom. It also notes where sources contradict each other, which is where the interesting findings tend to hide.

The output is only as good as the input. Forty solid interviews will give you something useful. Three vague ones won't.

Try: /synthesize-research onboarding interviews from Q3

3. /write-spec

As a PM who just got a one-line request like "can we add SSO," I want to turn it into a proper spec with goals, non-goals, and success metrics, so engineering and design are working from the same document.

It starts by asking about the user problem, who's affected, how you'll measure success, and any constraints, and it asks a few questions at a time instead of dumping a form on you. Then it writes a PRD with a problem statement, goals and non-goals, success metrics, acceptance criteria, and a phased plan if the request is too big to do at once. If your tracker or docs are connected, it can pull in related tickets and past specs.

Expect to edit the result. It gets you a solid structure and a first draft, and the product judgment in it still has to be yours.

Try: /write-spec centralized login for enterprise customers

4. /competitive-brief

As a product lead whose CEO just forwarded a competitor's launch post with "thoughts?", I want a researched brief on what they built and how they price it, so I can decide what to match and where to do something different.

It searches the web for the competitor's product and pricing pages, changelogs, press coverage, customer reviews on sites like G2 and Capterra, and even job postings, which can hint at where a company is headed. The result is a comparison with strengths, weaknesses, and positioning, and it can be shaped into a sales battle card or something for a board deck.

It's working from public information, so double-check anything that matters, especially pricing. Public pages go stale and hide a lot.

Try: /competitive-brief our top three rivals, focus on pricing and packaging

5. /roadmap-update

As a PM whose quarter just got a surprise enterprise deal and a slipped dependency on the same afternoon, I want to see what moves and what breaks downstream, so I can renegotiate the plan with facts.

You tell it what changed: a new item, a status change, a shifted date, or a full reprioritization. It asks why, applies a framework if one helps (RICE, MoSCoW, ICE, or value versus effort), and shows a before-and-after comparison, so the trade-offs are visible. It also flags downstream effects when a date moves. If you're starting from nothing, it can build a Now/Next/Later view.

Try: /roadmap-update add the partner API and tell me what has to give

6. /sprint-planning

As a PM or scrum master, I want capacity numbers that account for time off, meetings, and last sprint's leftovers, so we commit to what we can really finish.

Give it the team, the sprint length, the backlog, and any carryover. It estimates capacity after PTO and meetings, helps write the sprint goal, separates must-do work (P0) from stretch items, and points out dependencies and risks. With a project tracker and calendar connected it can pull that information itself.

Try: /sprint-planning Sprint 42, two weeks, six engineers

7. /metrics-review

As a product owner looking at a chart with a sudden drop in it, I want the numbers organized and compared against targets, so I know whether it's a real problem or noise.

It arranges your metrics from the North Star down to the smaller diagnostic ones, then checks each for current value, trend, distance from target, and whether the change is speeding up or slowing down. It also looks for anomalies and asks whether an overall trend is really coming from one segment. The end result is a scorecard with recommended actions.

If you don't have an analytics tool connected, paste in a table or describe the numbers. It will also ask about launches, outages, or seasonality that might explain a change, so have that context ready.

Try: /metrics-review last month, focus on activation and retention

8. /stakeholder-update

As a PM who writes the same status update four different ways every Friday, I want to give the facts once and get versions for each audience, so everyone gets what they need and I get some of my afternoon back.

It asks whether this is a weekly, monthly, launch, or one-off update, and who it's for: executives, engineers, cross-functional partners, customers, or the board. Then it adjusts the level of detail, tone, and jargon to match. Executives get the short version with the risk called out, engineers get the blocker and the decision needed, and customers get the benefit in plain language. Connected trackers, chat, and meeting notes feed in what happened since the last update.

Try: /stakeholder-update weekly, leadership, we're at risk on the migration

9. pptx

As a business lead with a board meeting on Thursday, I want my notes and numbers turned into a real PowerPoint file, so I can spend my time on the message instead of the formatting.

This skill creates and edits actual .pptx files, and it also works with templates, layouts, and speaker notes. It can read decks too, so you can hand it last quarter's presentation and ask for the three main messages.

One thing to know: if you ask for a deck without naming a file format, your setup may offer a dedicated slide format instead. Say "PowerPoint" or ".pptx" if that's what you need.

Try: "Turn this metrics review into a six-slide board update with speaker notes."

10. xlsx

As a founder or analyst whose quick forecast has turned into a spreadsheet the whole team depends on, I want clean data, working formulas, and sensible charts, so I can trust the numbers before I present them.

It builds and edits spreadsheet files (.xlsx, .csv, and similar), including cleaning up messy exports with junk rows or misplaced headers, computing formulas, formatting, and charting. It's a good fit when the spreadsheet itself is the deliverable.

Try: "Clean this export and build a revenue-by-segment model with a chart."

Two more worth knowing

skill-creator helps you turn your own team's playbook, such as your PRD template or launch checklist, into a reusable skill. docx is the one to use when a memo or report needs to arrive as a Word file.

Where to start

If you want a quick win, try /stakeholder-update or /write-spec, since most people have one of those due every week. If you're stuck at the beginning of something, start with /brainstorm or /synthesize-research.

Most of the PM commands work on their own with whatever you paste in. They do more when connected to your project tracker, docs, chat, and analytics. What's available depends on your setup, so check what's enabled in yours.