Product Strategy and Vision Doc
Write a product strategy that makes choices: diagnosis, target customer, 2-4 evidence-graded bets, a not-doing list, vision, and objectives.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a critical challenge for product leadership. You'll want to think about your company objectives first, then cascade those into team-level goals. Consider creating OKRs or KPIs that both teams can work toward. You might also review your competitive landscape to ensure your strategy is sound. Cross-functional alignment meetings are typically important. Do you have existing company goals you're building from, or should we start with your product vision?
COMPANY-TO-IC GOAL CASCADE Company OKR: Double revenue to 40M by end 2026 Product OKR: Increase paid user retention to 75% (currently 63%) Engineering OKR: Ship retention feature set, reduce onboarding friction Design OKR: Redesign onboarding flow, improve feature discoverability Q4 QUARTERLY PLAN Quarters 1-2: Research and design Quarters 3-4: Build and launch Resource allocation: 5 engineers, 2 designers, 1 PM Milestone: Beta launch to 500 users by Oct 15 Target: 68% retention by quarter end COMPETITIVE LANDSCAPE Direct competitors: three similar tools Retention leader uses: progressive feature unlock + weekly retention emails Our gap: no feature-readiness sequence TEAM ALIGNMENT FRAMEWORK Engineering focus: backend APIs for feature flagging, analytics instrumentation Design focus: form simplification, in-app tutorial sequence Product: weekly alignment reviews on flag rollout vs design updates Shared metric: daily active users retention week-over-week PRODUCT VISION DOCUMENT 90-day focus: build retention moat through personalized learning path Success definition: 68% W4 retention + engineering velocity of 8 features shipped Align by: Aug 5 kickoff with all leads DOCUMENT DELIVERED Quarterly plan, competitive analysis, vision charter, cascaded OKRs, resource map.
About this skill
Most product strategy drafts are goal lists or feature roadmaps with a vision paragraph on top. This skill writes a strategy that makes real choices and survives contact with capacity.
What it does
- Starts from a diagnosis of the critical challenge, not a goal
- Names the primary customer and the segments you will not optimize for
- Cuts to 2-4 bets, each with graded evidence, an early signal, and kill criteria
- Writes the not-doing list and a vision in the customer's language
- Derives product objectives with outcome key results and checks them against team capacity
What you get
A one-to-three page strategy document: diagnosis, who we serve, bets, not doing, vision, next-quarter objectives, capacity check, and open assumptions.
Best for
Heads of product and founders preparing annual planning, an offsite, or a board discussion.
SKILL.md preview
---
name: product-strategist
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.