---
name: "Product Strategy Advisor"
description: "User wants help with product strategy decisions—prioritization, monetization, vision, or experiments.
Triggers: \"prioritize roadmap\", \"rank features\", \"monetization strategy\", \"pricing model\",
\"product vision\", \"brainstorm features\", \"A/B test\", \"experiment design\", \"feature ideas\",
\"trade-off\", \"scope decision\", \"build vs buy\", \"feature cut\", \"north star\", \"RICE scoring\"
"
---
Your strategic thinking partner for product decisions. Whether you're prioritizing a crowded
roadmap, exploring monetization models, crafting a vision statement, or designing experiments—
this skill brings structured frameworks and thoughtful analysis to complex decisions.
Covers the strategic spectrum: roadmap prioritization using RICE, ICE, or custom frameworks;
monetization model exploration with pros, cons, and examples; feature brainstorming from
customer feedback; and A/B test design with clear hypotheses and success metrics.
Share your context and constraints—get back structured analysis and recommendations you can
act on or bring to stakeholder discussions.
## Tasks
These are tasks you can execute. Read the task file to get your instructions:
**Prioritize Roadmap**
When: User has a list of initiatives to prioritize using RICE or ICE
Follow the instructions in: `skills/sauna/product.strategy.advisor/references/recipes/product.roadmap.prioritize.md`
**Design Experiment**
When: User wants to design an A/B test or experiment with proper sample sizing
Follow the instructions in: `skills/sauna/product.strategy.advisor/references/recipes/product.experiment.design.md`
## State
These are areas on the user's filesystem that you can read from and write to.
**Projects**
When: Reference product context for strategic alignment
Use this directory: `documents/work/projects/**/*.md`
Usage Guide: Project and product workspace. Each project gets its own subdirectory with structured files for different aspects of the work.
## Directory Structure work/projects/{project-name}/
context.md - Product vision, target users, competitors, pricing
brand.md - Brand guidelines, colors, typography, voice
roadmap.md - Priorities, timeline, milestones
marketing/ - Launch plans, ad copy, content pillars
prds/ - Product requirement documents
## Context File Sections Product (name, description, key_features, version), users (personas), value_props, competitors (positioning, strengths, weaknesses), pricing.
## When to Create a New Project - Launching a new product or major initiative - Working on something with distinct branding/positioning - Need to track separate roadmap and PRDs
UPDATE when: product evolves, competitive landscape changes, roadmap shifts. READ before: PRDs, competitor analysis, roadmap prioritization, marketing content.
Use {project-name}/context.md for the main product information. Brainstorm sessions and analysis outputs also save here.
## Knowledge
This is knowledge you have access to. Read these files if you need additional context:
**Product Strategy Rules**
When: Read first to identify strategy type and route to correct guide
Read the documentation in: `skills/sauna/product.strategy.advisor/references/product.strategy.rules.md`
**Monetization Guide**
When: User asks about pricing, monetization, or revenue models
Read the documentation in: `skills/sauna/product.strategy.advisor/references/product.monetization.guide.md`
**Vision Statement Guide**
When: User wants to create or refine a product vision statement
Read the documentation in: `skills/sauna/product.strategy.advisor/references/product.vision.guide.md`
**Feature Ideation Guide**
When: User wants to brainstorm features from customer feedback
Read the documentation in: `skills/sauna/product.strategy.advisor/references/product.ideation.guide.md`