菜单
A hierarchical framework forcing alignment from top down—Mission, Company Strategy, Product Strategy, Roadmap, Goals. Strategy precedes goals; goals measure progress against a strategy.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Coowoolf/insighthunt-skills --skill product-strategy-stack命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical.
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
基于 SOC 职业分类
正在显示 SKILL.md
| name | Product Strategy Stack |
| description | A hierarchical framework forcing alignment from top down—Mission, Company Strategy, Product Strategy, Roadmap, Goals. Strategy precedes goals; goals measure progress against a strategy. |
"If you're going to take a road trip, you first decide where you want to drive to... our destination is Vegas, and we'll know whether or not we reach there if we've driven 250 miles." — Ravi Mehta
A hierarchical framework that forces alignment from top down. It separates mission (aspirational) from strategy (logical plan) and ensures the roadmap and goals are derivatives of the strategy, not the drivers.
┌─────────────────────────────────────────────────────────┐
│ MISSION │
│ The change you want to bring to the world │
│ (Aspirational, enduring) │
├─────────────────────────────────────────────────────────┤
│ COMPANY STRATEGY │
│ The logical plan to achieve the mission │
│ (Multi-year, company-wide) │
├─────────────────────────────────────────────────────────┤
│ PRODUCT STRATEGY │
│ Connective tissue between company and product │
│ (How product specifically contributes) │
├─────────────────────────────────────────────────────────┤
│ PRODUCT ROADMAP │
│ Sequence of features/outcomes to execute strategy │
│ (Quarterly/annual priorities) │
├─────────────────────────────────────────────────────────┤
│ PRODUCT GOALS │
│ Metrics that measure progress against roadmap │
│ (Lagging indicators of strategy execution) │
└─────────────────────────────────────────────────────────┘
Goals measure progress against a strategy. Without strategy, goals are arbitrary numbers.
Each layer must clearly derive from the one above.
Prevent misalignment by including visuals in strategy docs. Ambiguous text causes drift.
Mission doesn't change often. Strategy is how you achieve it in current conditions.
STEP 1: Articulate Mission
└── What change do we want in the world?
└── Why does this company exist?
STEP 2: Define Company Strategy
└── What is our logical plan?
└── What are we betting on?
STEP 3: Translate to Product Strategy
└── How does product specifically contribute?
└── What capabilities must we build?
STEP 4: Build Roadmap from Strategy
└── What features execute this strategy?
└── What's the sequence?
STEP 5: Set Goals to Measure
└── What metrics indicate strategy is working?
└── Goals are outputs, not inputs
❌ Starting with goals ("increase retention by 5%") and building backward
❌ Conflating roadmap with strategy
❌ Using goals as substitute for strategy
Tinder vs. Hinge: Both are dating apps. Tinder's mission is "Make single life fun" (Product Strategy: fast swiping, serendipity). Hinge's mission is "Designed to be deleted" (Product Strategy: anti-swipe, rich profiles). Their features differ because their Strategy Stacks differ.
Source: Ravi Mehta, Former CPO of Tinder, Lenny's Podcast