vision

Develop a project vision document with goals, users, and success criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hodor/claude-compass --skill vision-hodor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/hodor/claude-compass/tree/main/plugin/skills/vision
Command: npx skills add https://github.com/hodor/claude-compass --skill vision-hodor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring a project's vision and scope are clearly defined from the outset, reducing ambiguity and guiding specification development.

Core Features & Use Cases

  • Project Vision Capture: Systematically document the project's purpose, user needs, and problem space.
  • Spec List Generation: Identify and outline distinct needs that will each become a spec, promoting coherent project planning.
  • Vision Document Creation: Produce a comprehensive vision document with goals, users, success criteria, and project-level constraints.

Quick Start

Initiate the vision capture process by running the skill and provide a brief project description.

Frequently Asked Questions about vision

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

FAQPage Schema
Why do I need a project vision document before starting specification development?▼

A project vision document reduces ambiguity by clearly defining your project's purpose, user needs, and scope from the outset, which guides coherent specification development. It captures goals, success criteria, and project-level constraints.

How do I define project scope and generate a list of individual specs?▼

You define project scope and generate a spec list by running the skill with a brief project description, which systematically identifies and outlines distinct needs to produce a structured specification list.

Can I use this for early project phases to coordinate planning among team members?▼

Yes, this targets early project phases to facilitate effective planning and coordination among team members. It produces structured documentation that clarifies key needs and establishes a coherent project roadmap.

What is the best way to capture user needs and problem space for a new project?▼

The best way to capture user needs and the problem space is to systematically document them through a structured vision capture process, which requires your project details as input to produce a comprehensive reference.

Does creating a vision document require any specific technical dependencies?▼

No external dependencies are required. Creating a vision document relies solely on providing your project details as user input, utilizing internal scripts and references to structure the goals and constraints.