Vision

Create structured vision documents with scope levels, success criteria, and constraints.

Updated Aug 23, 2026

Search Tags:#planning #roadmap #strategy #vision #alignment #product

Ready to run

npx skills add https://github.com/kurko/ai-company-os --skill vision-kurko

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Vision
Source: https://github.com/kurko/ai-company-os/tree/main/skills/vision
Command: npx skills add https://github.com/kurko/ai-company-os --skill vision-kurko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vision documents solve the lack of clarity and alignment when starting new features, products, or company initiatives by providing a structured future direction.

Core Features & Use Cases

Scope levels: support vision documents at Feature, Epic, Product, and Company levels to match the initiative.
Guided template: include a reliable template with discovery prompts, constraints, and success criteria.
Open questions & alternatives: capture unresolved questions and multiple options to inform decision-making.
Workflow integration: anchors brainstorming, PRD references, and kickoff activities in product development.

Quick Start

Draft a Vision document for the upcoming product feature, outlining the problem, goals, scope, and success criteria.

Frequently Asked Questions about Vision

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

FAQPage Schema

How do I write a vision document for a new product feature?▼

To write a vision document for a new product feature, outline the problem, goals, scope, and success criteria using a guided template with discovery prompts to clarify direction and rationale.

What is a vision document in product management?▼

A vision document in product management is a structured artifact that solves lack of alignment when starting new initiatives by defining future direction, success criteria, and constraints across teams.

Can I use a vision document for company-level strategy instead of just features?▼

Yes, you can use a vision document for company-level strategy because it supports multiple scope levels including Feature, Epic, Product, and Company to match the scale of your initiative.

What's the best way to capture open questions and alternatives during product planning?▼

The best way to capture open questions and alternatives during product planning is to use a structured vision template that explicitly records unresolved questions and multiple options to inform decision-making.

When do I need to define a vision for a new initiative?▼

You need to define a vision for a new initiative when starting a new product or feature and you require clear alignment, structured direction, and documented constraints to guide strategy across teams.