pm-vision

Generate a product vision and stakeholder alignment plan from structured PMContext.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-vision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-vision
Source: https://github.com/Wcof/PMSkill/tree/main/skills/discovery/pm-vision
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams turn scattered product context into a clear, actionable vision and a practical stakeholder alignment plan. It prevents vague vision statements, non-measurable long-term goals, and weak communication plans that fail to drive decisions.

Core Features & Use Cases

  • Vision Statement Generation: Builds a product vision from PMContext using three required elements: emotional pull, feasibility, and strategic direction.
  • Time-Horizon Planning: Produces measurable 10-year, 3-year, and 1-year goals so the vision can connect to strategy and execution.
  • Stakeholder Mapping & Communication: Maps stakeholders into a power-interest grid and defines communication strategies, channels, frequency, and core messages for each group.
  • Use Case: When a PM has already created PMContext and now needs to align leadership, legal, users, and internal teams around a product direction, this Skill creates a vision document and stakeholder communication plan grounded in the same source material.

Quick Start

Ask the agent to run pm-vision after PMContext is ready to generate a product vision statement, measurable time ladder, stakeholder map, and communication plan.

Frequently Asked Questions about pm-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a measurable product vision from scattered product context?

To create a product vision from scattered context, structure your inputs into PMContext first. The tool then extracts user scenarios and validation metrics to generate a vision statement grounded in emotional pull, feasibility, and strategic direction.

How do I map stakeholders using a power interest grid for product alignment?

Mapping stakeholders with a power interest grid categorizes leadership, users, and internal teams by influence and interest. This defines targeted communication strategies, channels, frequency, and core messages to drive cross-functional alignment.

What is the best way to define measurable 10 year, 3 year, and 1 year product goals?

Defining measurable 10 year, 3 year, and 1 year product goals requires establishing a time ladder that connects your vision to execution. The tool generates these time horizons using extracted boundary conditions and value validation metrics from PMContext.

Do I need structured PMContext to generate a stakeholder communication plan?

Yes, you need structured PMContext to generate a stakeholder communication plan. The tool requires extracted user scenarios and boundary conditions from PMContext to produce traceable communication planning and accurate power interest grid mapping.

How to align cross-functional teams around a product direction without vague vision statements?

Aligning cross-functional teams requires translating PMContext into a clear vision and traceable communication plan. The tool prevents vague statements by enforcing measurable time horizons and explicit stakeholder mapping to drive actionable decisions.

Can I use this for roadmap framing and product strategy if my context lacks validation metrics?

No, you cannot effectively use this for roadmap framing and product strategy without validation metrics. The tool requires extracted value validation metrics and boundary conditions from PMContext to generate measurable goals and a feasible strategic direction.