product-strategy

Overview of product-strategy skill

What product-strategy does

The product-strategy skill helps you turn an early product idea, a messy briefing, or an existing product into a structured strategy using the Product Strategy Canvas. It is aimed at Product Management work where you need a clear answer to: what are we building, for whom, why this approach, and how will we win?

Who should use it

Use the product-strategy skill if you need a product strategy for a new product, a repositioning exercise, a launch plan, or a strategic planning deck. It is most useful when you already have some market context and need a sharper, more decision-ready strategy rather than generic brainstorming.

What makes it useful

The main value of this product-strategy skill is structure. Instead of producing a vague strategy memo, it forces coverage of vision, segments, relative cost, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. That makes it better than an ordinary prompt when you need a complete strategy frame that can be reviewed, challenged, and reused.

How to Use product-strategy skill

Install and locate the source

Install the product-strategy skill with npx skills add phuryn/pm-skills --skill product-strategy. After install, read SKILL.md first, then check whether your environment exposes supporting files in the repo path pm-product-strategy/skills/product-strategy. In this repository, there are no separate scripts or reference folders, so the core behavior lives in the skill instructions themselves.

Prepare a strong input brief

The product-strategy usage works best when you provide a concise but specific brief, not just “make a strategy.” Include the product, target customer, market stage, competitors, constraints, and the decision you want supported. A strong input looks like: “Create a product-strategy for a B2B analytics tool aimed at mid-market finance teams; we compete with spreadsheets and one enterprise vendor; we need a low-cost wedge and a defensible expansion path.”

Shape the prompt around the canvas

A good product-strategy guide prompt should ask for a full canvas, not a freeform essay. For example: “Draft a Product Strategy Canvas for [product], covering vision, first segment, cost position, value proposition, key trade-offs, core metrics, growth path, required capabilities, and defensibility. Call out assumptions where data is missing.” This keeps the output aligned with the skill’s intended workflow.

Use the output as a working draft

Treat the first pass as a strategy draft for critique. The most useful next step is to test whether the chosen first segment is realistic, whether the cost position matches the market, and whether the defensibility story is grounded in actual capabilities. If any of those are weak, revise the input and rerun the skill rather than polishing weak strategy language.

product-strategy skill FAQ

Is product-strategy for Product Management only?

It is most relevant for Product Management, but it also helps founders, strategy leads, and cross-functional teams that need a coherent product direction. If your task is to decide positioning, segment focus, and growth logic, the skill is a good fit.

How is this different from a normal prompt?

A normal prompt can produce a strategy-shaped answer, but the product-strategy skill gives you a consistent canvas and decision order. That reduces the chance of skipping hard questions like trade-offs, cost position, or defensibility, which are often the parts that make a strategy actually useful.

Do I need detailed market data first?

No, but stronger inputs produce better output. The skill can work from partial information, yet it is more effective when you provide competitor names, customer constraints, and a sense of what resources you can realistically deploy.

When should I not use this skill?

Do not use the product-strategy skill if you only need a short product brief, a launch checklist, or a marketing message. It is designed for strategic framing, so it is overkill when the job is simply to summarize a feature or write a lightweight plan.

How to Improve product-strategy skill

Give the skill a sharper decision context

The best way to improve product-strategy results is to state the decision you want to make. Say whether you need a wedge strategy, a category entry strategy, a turnaround plan, or a scale-up plan. That changes the trade-offs the skill should emphasize and prevents generic output.

Feed it real constraints, not just aspirations

The product-strategy skill becomes much stronger when you include budget limits, team size, timeline, regulated-market constraints, pricing boundaries, or distribution limits. These details force the strategy to be executable instead of idealized.

Ask for explicit assumptions and weak points

If the first draft feels too confident, ask the skill to label assumptions, unknowns, and risk areas section by section. This is especially helpful for market segments and defensibility, where weak evidence can otherwise be disguised as polished language.

Iterate by challenging the canvas

After the first pass, refine the prompt with the parts that matter most: “tighten the first segment,” “make the cost position premium instead of low-cost,” or “replace vague defensibility claims with capability-based ones.” That iterative loop is the fastest way to turn the product-strategy skill from a generic planning tool into a useful strategy aid.