Product Vision

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction.

Published by @Paweł Huryn·0 agent reads / 30d·0 saves·

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
  • Introducing the Product Strategy Canvas
  • From Strategy to Objectives Masterclass (video course)

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

product-management+1
0
SKILL0

Knowledge Management

Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.

customer-success+2
0
SKILL0

Customer Research

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

customer-success+1
0