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.
Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/product-strategy-session
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
---name: product-strategy-session
argument-hint: "[product or strategic question]"
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.
intent: >-
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.
type: workflow
---## 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
### Why This Works
- **Structured discovery:** Prevents jumping to solutions before understanding problems
- **Stakeholder alignment:** Creates shared mental model across exec, product, design, engineering
- **Validated strategy:** Tests assumptions before committing resources
- **Executable roadmap:** Connects high-level strategy to concrete work
### Anti-Patterns (What This Is NOT)
- **Not a feature brainstorm:** Strategy sessions frame problems, not just list features
- **Not waterfall planning:** Builds in feedback loops and iteration
- **Not a solo PM exercise:** Requires cross-functional participation
### When to Use This
- Launching a new product or major initiative
- Annual/quarterly strategic planning cycles
- Repositioning an existing product
- Onboarding new product leaders (align on strategy)
### When NOT to Use This
- When strategy is already clear and validated
- For tactical feature additions (no strategic shift needed)
- When you lack executive sponsorship (strategy won't stick)
---
### Facilitation Source of Truth
When running this workflow as a guided conversation, use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the interaction protocol.
