Product Strategy Session
Run a structured six-phase product strategy workshop—from positioning and JTBD through problem framing, opportunity trees, RICE prioritization, and exec alignment—before committing roadmap work.
Overview
Product Strategy Session is an agent skill most often used in Validate (also Build/pm and Idea/research) that runs a phased PM workshop from positioning through prioritization and alignment.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill product-strategy-sessionWhat is this skill?
- Six-phase flow: positioning → problem framing → opportunity-solution tree → RICE prioritization → stakeholder alignment
- Chains proto-personas, JTBD, and problem statements into scored epics and quarterly roadmap slices
- Uses RICE scoring with stage-aware prioritization advisor for early-PMF vs growth contexts
- Includes worked SaaS onboarding example (60% drop-off → guided checklist POC and Q1/Q2 roadmap)
- Forces experiment gates (e.g., 2-week prototype) when leadership challenges full-build commits
- 6-phase strategy session flow
- 3 opportunities and multiple solutions in OST example
Adoption & trust: 1.6k installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have product metrics and feature ideas but no shared positioning, problem statement, or prioritized roadmap your agent or team can execute against.
Who is it for?
Solo founders or indie PMs improving an existing SaaS or tool who need strategy artifacts before writing specs or implementation plans.
Skip if: Teams that already have an approved PRD and locked roadmap, or pure greenfield coding with no product hypotheses to test.
When should I use this skill?
You need end-to-end product strategy—from positioning through roadmap and alignment—not a single ad-hoc feature idea.
What do I get? / Deliverables
You leave with personas, a crisp problem statement, a chosen opportunity and POC, RICE-scored epics, a phased roadmap, and exec feedback folded into experiments before build.
- Positioning and proto-persona notes
- Problem statement and opportunity-solution tree selection
- RICE-scored roadmap and alignment narrative
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate because the session’s earliest gates (positioning, problem statement, POC choice) prove whether the opportunity is worth scoped investment before full Build execution. Scope is where you narrow who you serve, what problem you solve, and which epics hit the roadmap—exactly what this session outputs after prioritization and alignment.
Where it fits
Reframe target segment and JTBD before committing to a new vertical.
Turn 60% onboarding drop-off into a problem statement, OST, and POC checklist.
Convert RICE-scored epics into Q1/Q2 roadmap themes for the agent to plan against.
Re-run prioritization when retention experiments need the next highest-RICE initiative.
How it compares
Use instead of one-shot chat brainstorming when you need canvases, scoring, and alignment—not a single feature generator.
Common Questions / FAQ
Who is product-strategy-session for?
Solo builders and small teams who own product decisions and want agent-guided strategy sessions with prioritization and stakeholder-ready outputs.
When should I use product-strategy-session?
During Validate to scope retention or PMF bets; during Build/pm to refresh roadmap; during Idea/research when reframing positioning before you prototype or ship major onboarding changes.
Is product-strategy-session safe to install?
It is procedural documentation and examples—review the Security Audits panel on this Prism page before installing any repo skill.
SKILL.md
READMESKILL.md - Product Strategy Session
# Product Strategy Session Examples ### Example 1: Good Product Strategy Session (SaaS Onboarding Improvement) **Context:** Existing SaaS product with 60% onboarding drop-off, need strategic approach to retention. **Phase 1 - Positioning:** - Ran `positioning-workshop.md`: Defined target = "non-technical small business owners" - Created proto-personas: "Solo Entrepreneur Sam" (no IT support) - JTBD: "Help me get value from software fast without technical expertise" **Phase 2 - Problem Framing:** - Ran `problem-framing-canvas.md`: Problem = "Users abandon onboarding because jargon-heavy UI and lack guidance" - Problem statement: "60% of non-technical users drop off in first 24 hours due to overwhelming, unclear onboarding flow" **Phase 3 - Solution Exploration:** - Ran `opportunity-solution-tree.md`: Generated 3 opportunities (guidance, simplification, support) - Selected opportunity: "Lack of onboarding guidance" - Solutions: Guided checklist, tooltips, email drip, human-assisted onboarding - POC: Guided checklist (test with prototype) **Phase 4 - Prioritization:** - Ran `prioritization-advisor.md`: Recommended RICE (early PMF stage, some data) - Scored epics: Guided onboarding (RICE: 12,000), In-app help (8,000), Human onboarding (3,000) - Roadmap: Q1 = Guided onboarding, Q2 = In-app help **Phase 5 - Alignment:** - Presented to execs: Problem statement + OST + roadmap - Feedback: "Can we run experiment before full build?" → Added 2-week prototype test **Phase 6 - Execution:** - Ran `epic-breakdown-advisor.md`: Split "Guided onboarding" using workflow pattern - Stories: R1 = Simple checklist (3 steps), R2 = Progress tracking, R3 = Celebration/gamification - Planned Sprint 1: Build R1 (simple checklist) **Outcome:** Clear, validated strategy with executive buy-in and executable roadmap. --- ### Example 2: Bad Product Strategy Session (Skipped Discovery) **Context:** Startup wants to build mobile app. **Phase 1 - Positioning:** Skipped (assumed positioning was clear) **Phase 2 - Problem Framing:** Skipped (jumped to solution: "We need a mobile app") **Phase 3 - Solution Exploration:** Skipped (already decided on solution) **Phase 4 - Prioritization:** Built feature list, prioritized by "what's easiest" **Phase 6 - Execution:** Started building mobile app immediately **Why this failed:** - No positioning validation (who is the app for?) - No problem validation (do customers actually need mobile access?) - No alternative solutions explored (responsive web? PWA?) - 3 months later: Mobile app built, low usage, wrong problem solved **Fix with strategy session:** - Run positioning workshop: Discovered target = "field workers who can't access desktop" - Run problem framing: Validated that mobile-first users can't complete workflows on the go - Run OST: Explored alternatives (mobile app, responsive web, PWA, SMS notifications) - Run experiments: Tested responsive web first (2 weeks), validated it solved 80% of problem - Outcome: Built responsive web instead of native app, saved 2 months dev time --- --- name: product-strategy-session 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 fr