vision

Create, update, and validate project vision documents with guiding principles and success criteria.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/dwayneparton/claude --skill vision-dwayneparton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/dwayneparton/claude/tree/main/skills/vision
Command: npx skills add https://github.com/dwayneparton/claude --skill vision-dwayneparton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects often lack a clear strategic direction, causing misaligned decisions by contributors and AI agents. This Skill produces a VISION.md document that defines the project's purpose, success criteria, guiding principles, and boundaries so every change can be evaluated against a shared north star. ## Core Features & Use Cases - Structured Discovery: Analyzes the codebase, git history, and existing documentation to understand what the project actually is before writing anything. - Collaborative Clarification: Asks targeted questions based on project type (library, service, product, tool) to capture the user's intent and scope the document depth. - Actionable Vision Document: Generates a VISION.md with evaluable success criteria, principles with "which means" clauses, explicit boundaries, and quality standards. - CLAUDE.md Integration: Adds a reference to the vision in CLAUDE.md so all agents align their work with it. - Use Case: When starting a new open-source library, run this Skill to interview you about goals, analyze the repo, and produce a docs/VISION.md that future contributors and AI agents use to evaluate every feature proposal. ## Quick Start Ask the AI to create a vision document for this project and define its success criteria and guiding principles.

Frequently Asked Questions about vision

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

FAQPage Schema
How do I create a project vision document?

Run the vision skill, which analyzes your codebase and git history, asks targeted clarifying questions about goals and users, then writes a VISION.md with purpose, success criteria, guiding principles, and boundaries.

What should a project vision document include?

A vision document should include a mission statement, project type, concrete success criteria, guiding principles with actionable "which means" clauses, explicit boundaries defining what is out of scope, and quality standards.

Where should the vision document live in a repository?

The default location is docs/VISION.md. For small projects without a docs directory, VISION.md at the repository root works. If a vision document already exists elsewhere, it is updated in place.

Can the vision skill update an existing vision document?

Yes. The skill searches for existing vision, mission, strategy, or goals documents during discovery and reads them thoroughly. If one exists, the workflow shifts from creating to updating and refining it.

How does the vision document help AI coding agents?

The skill adds a reference to the vision in CLAUDE.md so agents read it before working. Agents use the guiding principles and boundaries to evaluate whether a feature, fix, or change aligns with the project's direction.

When should I not write a detailed vision document?

Small weekend side projects do not need multi-page visions. The skill scopes depth to the project, so a half-page vision may be appropriate for solo experiments while production platforms warrant detailed principles.