# How to Craft a Product Vision Using the product-vision Skill in pm-skills

> Learn to craft a compelling product vision using the product-vision skill in pm-skills. Follow a six-step workflow for inspiring, achievable, and resonant vision statements via CLI.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-06-27

---

**The `product-vision` skill in the phuryn/pm-skills repository provides a structured, six-step prompt workflow that generates inspiring, achievable, and emotionally resonant vision statements through CLI commands like `/product-vision` or integrated strategy tools.**

Crafting a compelling product vision requires balancing inspiration with practicality. The `product-vision` skill in the phuryn/pm-skills repository automates this process through a guided prompt framework defined in [`pm-product-strategy/skills/product-vision/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/product-vision/SKILL.md) that transforms raw product descriptions into concise north-star statements. This open-source tool leverages structured context gathering and iterative refinement to align teams around a shared future.

## What the product-vision Skill Does

The `product-vision` skill is a ready-to-use prompt that guides product managers through creating concise, inspiring, and achievable vision statements. According to the source code in [`pm-product-strategy/skills/product-vision/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/product-vision/SKILL.md), it processes inputs ranging from brief product descriptions to full strategy documents, then outputs **3-5 vision variants** each limited to a few sentences.

The skill produces vision statements that are threefold:

- **Inspiring** – Motivates the team and stakeholders toward a common goal.
- **Achievable** – Realistic given current resources and market dynamics.
- **Emotional** – Connects on a human level rather than offering purely functional descriptions.

## The Six-Step Framework for Crafting Product Visions

The skill follows a structured methodology implemented in the underlying prompt logic. When you invoke the tool, it executes this sequence:

### 1. Gather Context

Provide the skill with existing product descriptions, market positioning statements, company mission documents, or other relevant material. The system analyzes these inputs to establish baseline constraints and opportunities.

### 2. Identify the Core Problem

The skill extracts the fundamental problem your product solves for its users. This step ensures the vision remains rooted in genuine user needs rather than feature specifications.

### 3. Envision the Ideal Future

You are prompted to imagine the best-possible outcome for both customers and the business. This step focuses on the transformation your product enables, not just the mechanics of how it works.

### 4. Draft Multiple Options

Based on the gathered context, the system generates **3-5 vision variants**, each limited to a few sentences. This provides alternatives ranging from pragmatic to aspirational.

### 5. Select and Refine

You choose the strongest version from the generated options, optionally adding a short rationale that explains why this vision resonates with your product strategy.

### 6. Align with Values and Opportunity

The final vision is explicitly tied to company values, market opportunity, and a clear north-star metric, ensuring it serves as a practical guiding principle rather than vague platitudes.

## How to Use the product-vision Skill

The skill can be accessed through direct CLI commands or integrated workflows. Below are practical implementations based on the command definitions in the repository.

### Basic Invocation with Product Description

Submit a concise product description directly to the command:

```text
/product-vision AI-powered design tool for non-designers

```

**Result example:**

> **Vision** – "Empower every creator, regardless of skill, to design professional-grade graphics instantly, turning ideas into visual reality with a single click."

### Processing Uploaded Strategy Documents

Reference existing documentation to ground the vision in established strategy:

```text
/product-vision [upload: existing_strategy.pdf]

```

**Result example:**

> **Vision** – "Make design effortless for non-designers worldwide, delivering AI-driven, on-demand graphics that let anyone bring their ideas to life without learning complex tools."

### Interactive Context Gathering

When run without arguments, the skill enters an interactive mode to collect necessary context:

```text
/product-vision

```

The system will prompt you with specific questions:

- "What does the product do?"
- "Who is the primary user?"
- "What stage are you at (idea, MVP, growth)?"

After you provide answers, the skill returns a set of vision drafts to choose from.

### Integration with the Strategy Command

The `product-vision` skill serves as the foundation for the broader strategy workflow. When you run the comprehensive strategy command documented in [`pm-product-strategy/commands/strategy.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/commands/strategy.md), it automatically applies the vision skill before proceeding to subsequent sections:

```text
/strategy AI-powered design tool for non-designers

```

**Output snippet:**

```markdown

### 1. Vision

Empower every creator, regardless of skill, to design professional-grade graphics instantly, turning ideas into visual reality with a single click.

### 2. Target Segments

| Segment | Size | Pain Level | Current Alternative | Priority |
|---------|------|-----------|---------------------|----------|
| ... |

```

## Source Code and Implementation Files

The `product-vision` skill is implemented across several files in the phuryn/pm-skills repository:

| File | Role |
|------|------|
| [`pm-product-strategy/skills/product-vision/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/product-vision/SKILL.md) | Defines the skill metadata, input requirements, and the six-step process. |
| [`pm-product-strategy/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/README.md) | Lists the skill among the product-strategy toolkit with usage descriptions. |
| [`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md) | Provides a high-level overview of all available skills including `product-vision`. |
| [`pm-product-strategy/commands/strategy.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/commands/strategy.md) | Demonstrates integration of the vision skill within the broader strategy command. |

## Summary

- The `product-vision` skill provides a **six-step structured workflow** for generating vision statements: Gather Context, Identify Core Problem, Envision Ideal Future, Draft Options, Select and Refine, and Align with Values.
- Use the **`/product-vision`** command followed by a description, document reference, or no arguments for interactive mode.
- The skill outputs **3-5 variants** that are inspiring, achievable, and emotionally resonant.
- Vision creation is automatically integrated into the **`/strategy`** command workflow as the first step of the Strategy Canvas.
- Source definitions reside in [`pm-product-strategy/skills/product-vision/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/product-vision/SKILL.md) within the phuryn/pm-skills repository.

## Frequently Asked Questions

### How does the product-vision skill differ from generic AI writing prompts?

The `product-vision` skill is specifically engineered with a structured six-step methodology defined in [`pm-product-strategy/skills/product-vision/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/product-vision/SKILL.md) that forces consideration of user problems, business values, and north-star metrics. Unlike generic prompts, it requires interactive context gathering and outputs multiple variants tied to strategic constraints rather than prose generation.

### Can I use the product-vision skill with existing strategy documents?

Yes. The skill accepts document uploads using the syntax `/product-vision [upload: filename.pdf]`. This allows the system to extract context from existing strategy materials, ensuring the generated vision aligns with previously established market positioning and company mission statements.

### What makes a vision statement "achievable" according to the skill criteria?

According to the implementation in the phuryn/pm-skills source code, an achievable vision is one that is realistic given your current resources and market dynamics. The skill specifically filters out purely aspirational statements that lack feasible execution paths, ensuring the final output can serve as an actual north-star metric for product development.

### How does the product-vision skill integrate with the broader strategy workflow?

The skill is the first automated step when using the `/strategy` command as documented in [`pm-product-strategy/commands/strategy.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/commands/strategy.md). After generating the vision, the workflow automatically proceeds to populate the remaining sections of the Strategy Canvas, including target segments, value proposition, and go-to-market considerations, using the vision as the foundational alignment point.