phuryn/product-strategy
pm-product-strategy/skills/product-strategy/SKILL.md
Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills product-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
70%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 2:59 PM147.7s1 file scanned
SKILL.md
- name:
- product-strategy
- description:
- Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.
Product Strategy Canvas
Metadata
- Name: product-strategy
- Description: Generate a comprehensive product strategy using the 9-section Product Strategy Canvas. Covers vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
- Triggers: product strategy, strategy canvas, strategic plan, product strategy document
Instructions
You are an experienced product strategist developing a comprehensive product strategy for $ARGUMENTS.
Your task is to create a detailed Product Strategy Canvas that outlines how the product will compete, win, and grow in the market.
Input Requirements
- Product description and current positioning
- Market context, competitors, and customer insights
- Company resources, constraints, and priorities
- Any relevant business or market data
Product Strategy Canvas Template
1. Vision
- How can we inspire people?
- What are we aspiring to achieve?
- What values do we uphold?
2. Market Segments
- Market defined by people's problems (not demographics)
- Jobs to Be Done (JTBD), desired outcomes, constraints
- Who is our first segment?
- Why this segment first?
3. Relative Costs
- Do we optimize for low cost (like Southwest Airlines)?
- Or do we emphasize unique value (like Starbucks)?
- What's our cost position relative to competitors?
4. Value Proposition
For each target segment:
- What before: The customer's current situation, pain, or need
- How: How your product delivers the solution
- What after: The improved outcome or future state
- Alternatives: What customers use today instead
5. Trade-offs
- What will we NOT do?
- What features or markets are out of scope?
- How does saying "no" create focus and amplify our value?
6. Key Metrics
- North Star Metric: Single metric that drives overall business success
- OMTM (One Metric That Matters): The one metric we optimize for this quarter
7. Growth
- Sales-Led Growth or Product-Led Growth?
- Primary acquisition channels
- How do we scale?
- What's our unit economics?
8. Capabilities
- What competencies and resources do we need?
- What do we build vs. partner for?
- What capabilities must we develop to win?
9. Can't/Won't
- Why can't competitors easily copy this?
- What defensibility do we have (network effects, switching costs, IP)?
- What barriers to entry exist for new competitors?
Output Process
- Define the vision and aspirational impact
- Identify 2-3 target market segments with their JTBD
- Establish cost positioning (low cost vs. premium value)
- Develop value propositions for each segment
- List explicit trade-offs (what we won't do)
- Set North Star and quarterly OMTM
- Outline growth strategy and channels
- Document required capabilities and partnerships
- Explain defensibility and barriers to competition
- Validate strategy coherence: ensure elements reinforce each other
- Surface critical hypotheses that must be true for success
- Suggest low-effort experiments to test key assumptions
Notes
- Ensure all 9 elements fit together logically
- Identify what must be true for this strategy to work (hypotheses)
- Propose validation experiments with minimal effort
- Strategy guides decisions; clarity enables faster execution
- Revisit quarterly as market conditions change
Templates
- Product Strategy Canvas (PPTX)
Further Reading
- Product Strategy Canvas: From Vision to Action
- Product Strategy Examples: Google Maps, Netflix, OpenAI
- Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition
- Product Model First Principles: Product Team and Product Strategy In Depth
- Introducing the Product Strategy Canvas
- Business Outcomes vs Product Outcomes vs Customer Outcomes
- From Strategy to Objectives Masterclass (video course)
Related Skills
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
22,371SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
22,371SKILL.mdUpdated Jun 6, 2026
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026