product-strategy-session

Guide product managers through a 2–4 week strategy session producing validated artifacts.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/omeragaakbas/zoyare --skill product-strategy-session-omeragaakbas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-strategy-session
Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/product-strategy-session
Command: npx skills add https://github.com/omeragaakbas/zoyare --skill product-strategy-session-omeragaakbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often proceed to execution without validated customer context, clear positioning, or a prioritized roadmap, resulting in wasted effort and misaligned teams. This workflow turns vague strategic direction into a validated product strategy by orchestrating positioning, discovery, solution exploration, prioritization, stakeholder alignment, and execution planning across focused phases.

Core Features & Use Cases

  • End-to-end orchestration: Coordinates six phases—positioning, problem framing, solution exploration, prioritization, stakeholder alignment, and execution planning—into a repeatable 2–4 week process.
  • Practical artifacts: Produces positioning statements, proto-personas, JTBD, problem statements, opportunity-solution trees, epic hypotheses, prioritized epics, and a sequenced roadmap ready for execution.
  • Decision points & validation: Built-in checkpoints to require discovery interviews or experiments when uncertainty is high, preventing premature commitments.
  • Use Cases: Launching a new product, annual/quarterly strategic planning, major repositioning, or onboarding new product leadership to align on strategy.

Quick Start

Run a product strategy session to define the target customer and problem, validate hypotheses with discovery, and produce a prioritized roadmap with recommended experiments.

Frequently Asked Questions about product-strategy-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague product strategy into a validated roadmap?

To turn vague product strategy into a validated roadmap, orchestrate a structured strategy session covering positioning, customer discovery, and prioritization. This process produces positioning statements, proto-personas, and a sequenced roadmap with built-in validation checkpoints.

What is the best way to frame customer problems and explore solutions for a new product?

The best way to frame customer problems is by developing proto-personas, Jobs-to-be-Done, and problem statements. You then explore solutions by building opportunity-solution trees and formulating epic hypotheses to validate assumptions before committing to execution.

How do I align cross-functional teams on product prioritization and epics?

Align cross-functional teams on product prioritization by running a structured stakeholder alignment phase. This ensures shared understanding during solution exploration and results in mutually agreed, prioritized epics ready for execution planning.

Can I use this product strategy process for a 2-4 week quarterly planning engagement?

Yes, you can use this product strategy process for a 2-4 week quarterly planning engagement. It coordinates positioning, problem framing, prioritization, and execution planning into a repeatable workflow suitable for cross-functional teams.

When should I require discovery interviews or experiments during product planning?

You should require discovery interviews or experiments during product planning when uncertainty is high. Built-in decision points enforce these validation steps to prevent premature commitments and wasted effort on unvalidated product strategies.

What artifacts do I need to produce a sequenced roadmap from strategic ambiguity?

To produce a sequenced roadmap from strategic ambiguity, you need to generate positioning statements, proto-personas, JTBD, opportunity-solution trees, and prioritized epic hypotheses. These artifacts bridge the gap between discovery and execution planning.