product-strategy-session

Guide product managers through a six-phase strategy workflow from positioning to execution planning.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill product-strategy-session-sicktastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-strategy-session
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/product-strategy-session
Command: npx skills add https://github.com/sicktastic/skill-issue --skill product-strategy-session-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow prevents product teams from building roadmaps without validated positioning, problem framing, and stakeholder alignment, ensuring strategy is clear before execution begins.

Core Features & Use Cases

  • Six-phase orchestration that runs positioning, discovery, solution exploration, prioritization, alignment, and execution planning across 2-4 weeks.
  • Decision points and optional experiments safeguard against leaping ahead without validated customer context or uncertainty testing.
  • Use Case: When launching a major initiative, convene workshops, discovery interviews, and roadmap scoring to present a cohesive strategy with executive buy-in.

Quick Start

Run a product strategy session that confirms positioning, validates the core problem, explores solution hypotheses, and outputs a prioritized roadmap with stakeholder alignment.

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 direction into a validated product strategy?

To turn vague direction into a validated product strategy, use a structured workflow that orchestrates positioning, problem framing, and discovery. This ensures your team validates customer context and aligns stakeholders before committing to roadmap execution.

What is the best way to align stakeholders before committing to roadmap execution?

Stakeholder alignment requires structured workshops that validate positioning, frame the core problem, and explore solutions before roadmap planning. Running this workflow secures executive buy-in by presenting a cohesive, validated strategy with built-in decision points.

How do I run product discovery and prioritization for a multi-week initiative?

Run product discovery and prioritization by orchestrating interviews and solution exploration across a 2-4 week period. This guides teams through scoring and validating hypotheses, ensuring prioritization is backed by tested customer context and optional experiments.

When do I need to use decision points and optional experiments in product strategy?

Decision points and optional experiments are needed when building roadmaps for major initiatives without validated customer context. They safeguard against leaping ahead during product discovery, ensuring uncertainty is tested before execution planning begins.

Can I use this workflow for a major initiative requiring cross-functional positioning and executive buy-in?

Yes, this workflow is designed for major initiatives requiring cross-functional positioning and executive buy-in. It convenes workshops and discovery interviews across multiple phases to present a cohesive, validated product strategy to leadership.

What are the limitations of building roadmaps without validated positioning and problem framing?

Building roadmaps without validated positioning and problem framing risks executing on untested assumptions and lacking stakeholder alignment. Without structured discovery and decision points, teams build solutions that miss core customer context and fail to secure buy-in.