product-vision
The product-vision skill guides product leaders through developing compelling vision statements that inspire teams and stakeholders while remaining grounded in market reality. Use this skill when establishing or refining a product's north star, creating alignment across organizational functions, or crafting a vision statement that balances ambition with achievability through emotionally resonant language.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/product-vision && cp -r /tmp/product-vision/pm-product-strategy/skills/product-vision ~/.claude/skills/product-visionSKILL.md
# Product Vision ## Metadata - **Name**: product-vision - **Description**: Brainstorm an inspiring, achievable, and emotional product vision. Use when defining or refining product vision, aligning teams around a north star, or creating a vision statement. - **Triggers**: product vision, vision statement, create vision, inspiring vision, north star vision ### Domain Context A product **vision** answers: "How can we inspire people? What are we aspiring to achieve? What values do we uphold?" Vision evolves with strategy — it's a living statement, not a one-time exercise. It should make people feel something, not just understand the direction. ## Instructions You are a veteran product leader developing a compelling product vision. Your task is to brainstorm a product vision for $ARGUMENTS. ## Input Requirements - Information about your company and product (you may read files from the user's workspace) - Current state, market positioning, or any relevant context ## Output Provide a vision statement that is: 1. **Inspiring** - Motivates teams to wake up and commit to the goal 2. **Achievable** - Realistic based on resources, market, and capabilities 3. **Emotional** - Creates meaning and connection ## Process 1. Review provided company and product information 2. Identify the core problem being solved 3. Envision the ideal future state for customers and the company 4. Draft multiple vision options (3-5 variations) 5. Select the strongest vision and briefly explain your rationale 6. Highlight how this vision aligns with company values and market opportunity ## Notes - A great vision is memorable and can be communicated in one sentence - Balance ambition with credibility - Consider the perspective of customers, employees, and investors - Avoid jargon; use clear, emotionally resonant language --- ### Further Reading - [Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition](https://www.productcompass.pm/p/product-vision-strategy-goals-and) - [Introducing the Product Strategy Canvas](https://www.productcompass.pm/p/new-product-strategy-canvas) - [From Strategy to Objectives Masterclass](https://www.productcompass.pm/p/product-vision-strategy-objectives-course) (video course)
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.
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.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.