vision

Create a 500-700 word vision document saved to docs/vision.md.

26|2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/howells/arc --skill vision-howells
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vision
Source: https://github.com/howells/arc/tree/main/skills/vision
Command: npx skills add https://github.com/howells/arc --skill vision-howells

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams crystallize and maintain a clear project vision to align goals, scope, and decisions across stakeholders, reducing drift and misalignment.

Core Features & Use Cases

  • Vision drafting: Generate a concise 500-700 word vision document that outlines purpose, goals, and non-goals.
  • Guided Context Harvesting: Walks through one-question-at-a-time prompts to gather essential context.
  • Interoperability: Produces a docs/vision.md file and reads existing visions for updates in future sessions.
  • Use Case: When initiating a new project, run this to produce a shared North Star document for all collaborators.

Quick Start

Use the vision skill to create or update docs/vision.md. Start by answering the prompts when asked.

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 for stakeholders?

To create a project vision document, this skill guides you through one-question-at-a-time prompts to gather context, generating a 500-700 word markdown file covering purpose, goals, and non-goals.

What should be included in a project vision to align stakeholders?

A project vision should include Purpose, Goals, Target Users, Success Criteria, Non-Goals, and Principles. This skill systematically captures these elements to prevent scope drift and misalignment.

Can I update an existing vision markdown file without starting over?

Yes, you can update an existing vision markdown file. The skill reads existing docs/vision.md files to refine and maintain your project vision during future sessions without starting from scratch.

What is the best way to define non-goals for project planning?

The best way to define non-goals for project planning is through guided context harvesting. This skill prompts you one question at a time to explicitly outline boundaries, reducing team misalignment.

Does generating a vision document require any external dependencies?

No, generating a vision document requires zero external dependencies. The skill operates independently to harvest context and output the final markdown file directly to your docs folder.