# Product Strategy Session

Run an end-to-end product strategy session across positioning, discovery, and roadmap...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill product-strategy-session -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill product-strategy-session -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill product-strategy-session -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill product-strategy-session -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Purpose
Guide product managers through a comprehensive product strategy session by orchestrating positioning, problem framing, customer discovery, and roadmap planning skills into a cohesive end-to-end process. Use this to move from vague strategic direction to concrete, validated product strategy with clear positioning, target customers, problem statements, and prioritized roadmap, ensuring alignment across stakeholders before committing to execution.

This is not a one-time workshop, it's a repeatable process for establishing or refreshing product strategy, typically spanning 2-4 weeks with multiple touchpoints.

## Input

**Works best with:** The product (or product line) and the strategic question forcing the session.
**Also useful:** Existing positioning, discovery artifacts, roadmap drafts, and who needs to align on the outcome.

Anything supplied with the invocation itself, text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line, counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The workflow starts at positioning and orchestrates the phases from there, supplied artifacts let it skip ahead.

**Example invocation:** `Run a strategy session for our analytics add-on: flat adoption, two competing roadmap visions, exec review in 4 weeks.`

## Key Concepts

### What is a Product Strategy Session?

A product strategy session is a structured, multi-phase process that takes a product from strategic ambiguity to validated direction. It orchestrates:

1. **Positioning & Market Context**, Define who you serve, what problem you solve, and how you're differentiated
2. **Problem Discovery & Validation**, Frame and validate customer problems through research
3. **Solution Exploration**, Generate opportunity solutions and prioritize based on impact
4. **Roadmap Planning**, Sequence epics and releases based on strategy

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/product-strategy-session/SKILL.md