define-vision

Name: define-vision
Availability: InStock
Author: capataina

Generates a VISION.md fileCapturing project goals, scope, and design intent from guided team discussions.

Updated Mar 22, 2026

Search Tags:#roadmap #vision #product #define #stakeholders #design-pillars

Ready to run

npx skills add https://github.com/Capataina/agent-skills --skill define-vision-capataina

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: define-vision
Source: https://github.com/Capataina/agent-skills/tree/main/define-vision
Command: npx skills add https://github.com/Capataina/agent-skills --skill define-vision-capataina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams articulate and refine a clear product vision through a guided, question-driven session, producing a concrete, shared reference document.

Core Features & Use Cases

Interactive discovery: guides stakeholders through purpose, design pillars, audience, constraints, and non-goals to reach precise decisions.
Artifact generation: outputs docs/VISION.md that can be used to align roadmaps, features, and success criteria.
Guardrails for clarity: enforces specificity and prevents vague statements by asking targeted follow-ups.

Quick Start

Begin by launching the define-vision skill and sharing high-level context to start shaping the vision.

Frequently Asked Questions about define-vision

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

FAQPage Schema

How do I create a clear product vision with stakeholders?▼

To create a clear product vision with stakeholders, use a guided, question-driven session that articulates purpose, design pillars, audience, constraints, and non-goals. This structured approach ensures precise decisions and outputs a shared reference document for the team.

What is a product vision document and what should it include?▼

A product vision document defines the project's core purpose, design pillars, target audience, constraints, and explicit non-goals. It serves as a concrete, shared reference to align roadmaps, features, and success criteria across the product team.

How do I align stakeholders on product goals and non-goals?▼

Align stakeholders on product goals and non-goals through interactive discovery sessions that enforce specificity and prevent vague statements. By asking targeted follow-ups about constraints and design pillars, you guide the group to reach precise, shared decisions.

Can I use a structured conversation to define design pillars for an early-stage project?▼

Yes, you can define design pillars for early-stage projects through a structured conversation. This interactive discovery process applies to refinement sessions, guiding stakeholders to articulate specific pillars and constraints to shape the product direction.

What is the best way to prevent vague statements when defining a product vision?▼

The best way to prevent vague statements when defining a product vision is to apply guardrails for clarity during the discussion. This involves asking targeted follow-up questions that enforce specificity regarding the product's purpose, audience, and constraints.

How do I validate product vision criteria for subsequent roadmap planning?▼

Validate product vision criteria by generating a concrete artifact like docs/VISION.md during your alignment session. This document provides the specific inputs and concrete criteria required to validate features and align subsequent roadmap planning effectively.